Replies: 7 comments
-
Option: We could create executable installers using pynsist. These could be posted on the github page under the releases section along with the release notes. |
Beta Was this translation helpful? Give feedback.
-
This guy has made a detailed website about own personal headaches: https://sonotley.github.io/python-deployment-docs/tldr/ |
Beta Was this translation helpful? Give feedback.
-
A spyder dev suggests this for scientific packages: https://github.com/conda/constructor, though spyder actually uses pynsist for their new spyder standalone installer. |
Beta Was this translation helpful? Give feedback.
-
The poetry package gets referenced a lot when it comes to python packaging. I once read a very long blob post by a poetry fan, waiting for the actual point to arrive, and it never did. I guess it's worth another look. |
Beta Was this translation helpful? Give feedback.
-
Another option is to manually run This is actually a pretty simple solution. We could get the GH Actions to generate this file and inlcude it in the release notes along with the changelog. |
Beta Was this translation helpful? Give feedback.
-
Your final suggestion is a commonly used pattern (both in conjunction with conda and pip). The only caveat is that you may need to maintain one requirement file per python version that you aim to support (see, e.g. here). |
Beta Was this translation helpful? Give feedback.
-
There is also this: https://github.com/pypa/pipx |
Beta Was this translation helpful? Give feedback.
-
My recent descent into dependency hell has me thinking about making truly 'archived' installations. I'm opening this issue to capture the ideas and options.
Beta Was this translation helpful? Give feedback.
All reactions