-
Notifications
You must be signed in to change notification settings - Fork 14
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
Why not post package to pip? #30
Comments
Hi @jgostick, that's a good comment. I think the difficulty with posting the package is that PTV requires somewhat of a complex process to use, so installing it just to have it as an importable package will not be enough for most of the potential users. On the other hand, when someone downloads the source code from Github, they have also the manual, the example folder, and the workflow script that are supposed to help streamlining the processes so this is the solution we have t the moment. |
I just installed it with For our packages, which also have an examples folder that is not part of the pypi package, we just assume the user will get the code from pypi then refer to the github site for help, and this seems to work well. In fact, we get github actions to generate a fancy website using sphinx (see here), but this takes some effort. If your package becomes popular, then you may want to go for it. |
Thanks a lot for the tip, it sounds like a good way to go and the PoreSpy wedsite looks really awesome. I will probably go through with something like that soon enough. |
Is there any particular reason that your installation instructions require download source code and running pip? Why not post the package to pip and/or conda-forge?
The text was updated successfully, but these errors were encountered: