-
Notifications
You must be signed in to change notification settings - Fork 1.3k
[FEATURE] Improve requirements #155
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
If this sounds useful, I'm happy to implement it myself and post a PR. |
We no longer have a `requirements.txt` file Refs: OthersideAI#155
@mjspeck this could make sense. Is it sufficient that |
I haven't had issues on my side. I just think long term it will be better to deal with this now. Leaving the issue lingering will make it harder to deal with and dependency hell is something to avoid at all costs IMO. |
@mjspeck I am curious for the reason for removing |
It's just not necessary anymore. Everything defined in |
You don't need |
@mjspeck ok, thanks for the input. I'll take a closer look at this switch |
Thank you! My PR should be pretty straightforward |
Is your feature request related to a problem? Please describe.
A cleaner way to manage dependencies is crucial at the beginning of a project to reduce technical debt and allow collaboration and development. The current
requirements.txt
has a ton of pinned dependencies which is not optimal and very difficult to update.Describe the solution you'd like
I propose using a dependency manager like Poetry or PDM (my preference) to handle this and to replace the current
requirements.txt
. This would mean a few files would be added:pyproject.toml
pdm.lock
And some removed:
requirements.txt
setup.py
The text was updated successfully, but these errors were encountered: