| Issue 7: | release this on pypi | |
| 1 person starred this issue and may be notified of changes. | Back to list |
I don't generally like to just copy files into my projects from SVN trunks. I know it's just one file, but it'd be nice if this was released as a package to pypi.
Apr 6, 2009
Project Member
#1
gtempacc...@yahoo.com
Apr 7, 2009
I have strong preferences about the release process myself, so I'll just indicate them. I'd prefer it the tarball worked with at least distutils (or setuptools, your choice), and thus has a setup.py. I also strongly prefer for the release to be on pypi, not just a release on this site. I rely on automated tools (buildout) to create projects from a whole bunch of packages, and they prefer this kind of release (though it can be made to work with anything). I'd also suggest you upload your tarball directly to pypi, as I've had some frustration with downloading tarballs from sites that pypi just links to (those sites can go down as well, introducing multiple points of failure. not that I expect code.google.com to be down a lot, but it's the principle of the thing). If you need help with the packaging process let me know and I can take a look at it if you'd like.
Apr 7, 2009
Sure, if there is some automatic process that you are relying on that uses PyPI, I certainly don't mind if you want to check in some scripts and documentation to standardize this process. I will review the patches. As mentioned, the only real release criteria now is that the tests pass, and that takes like 20 seconds or less. :) Please coordinate with me about the description and version. Roughly I think the Python version feels like a 0.5 release, no? It's ready to use in a real project, so it's not 0.1. On the other hand, we are adding some stuff, like the formatters conversation you see on the mailing list. (Although that's not in the core language.) This would only cover the Python case though.
May 31, 2009
Martijn, thanks for taking care of this.
Status:
Fixed
Owner: martijn.faassen |