-
Notifications
You must be signed in to change notification settings - Fork 25
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
Installation problems with up-to-date libraries #19
Comments
Hi, The requirements.txt was generated with version numbers that were the latest at that time. I think most of these dependencies are backward compatible and you could just install the latest version and the code should still work. If not, you can post any issues here and we can look into it |
Hi Gilles, thanks for your answer. Something interesting that happened when I tried to install it in other ways is that the function Is there a way to install it in the original way but not have the package versions as hard requirements? Or what do you suggest? |
Hi @aendrs It could indeed be that the version deployed to PyPi (which is the one you'd obtain when running
This should add the gendis repo to your dist-packages such that you can import it from anywhere in your environment. The import statements in the gendis code itself will then make use of the latest versions of these dependencies. |
Hi Gilles, thanks for the suggestion. I will try to create a new environment and set it up as you suggest, it seems to be what I need to avoid internal conflicts. |
Feel free to do a pip freeze of your environment once you set it up correctly, such that I can update requirements.txt accordingly (I do not use virtual environments so rather hard to make a good update). |
Hi Gilles, after some months doing other projects and using a previously installed Gendis version in an isolated environment I decided to properly install it in a new environment. I did what you suggest, cloning the environment and installing it with :
What do you suggest?
|
Strange indeed 🤔. If you are in a virtual environment, you can probably run |
Is this package still supported? It seems that the requirements in the installation procedure are outdated and interfere with an up-to-date environment, making the installation difficult and inconvenient in a regular situation.
The text was updated successfully, but these errors were encountered: