-
Notifications
You must be signed in to change notification settings - Fork 30
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
Publish to PyPI #8
Comments
I went ahead and registered it on PyPI myself. Happy to transfer ownership of it when someone is ready to do this. |
+1 |
The package on PyPI needs to be updated to 0.2 |
@paste Thanks for the heads up. We no longer use InfusionSoft at my employer, so I'm not interested in spending time on work that InfusionSoft ought to be doing themselves. I would be happy to transfer the PyPI project to someone else, though I'd prefer to transfer it to a committer on this project. What say you, @MicFai or @andrewryno or @joshourisman or @kressaty? |
We're actually not really using infusionsoft anymore either… so it probably doesn't make sense for me to takes over the PyPI project. |
+1 |
Hey @nicksloan, I'd be happy to take this over if you're open to it. |
@RobertCalise That would be great. What is your PyPI username? |
@nicksloan Same as here, @RobertCalise |
@RobertCalise done! Thanks so much! |
In a similar vein to the previous setup.py issue, it would be helpful if this package were properly published on PyPI. Currently, an unofficial client is on PyPI with the name "infusionsoft". It would be great to reserve an alternative canonical name for this project on PyPI so that it can more easily be used with the Python packaging/installer machinery, namely the install_requires section of setup.py, and the requirements.txt file.
The text was updated successfully, but these errors were encountered: