<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Dec 23, 2009, at 4:33 PM, Lennart Regebro wrote:</div><blockquote type="cite"><div><blockquote type="cite"><font class="Apple-style-span" color="#000000"><br></font></blockquote><blockquote type="cite">1/ Missing packages (eg: Twisted is not there)<br></blockquote><br>The Twisted guys do not upload their packages to PyPI. I think that's<br>a mistake, but it's hardly PyPI's fault. There is no law saying you<br>have to use CPAN either.<br></div></blockquote></div><br><div>For what it's worth, we don't upload because it's a big pain, and nobody cares anyway.</div><div><br></div><div>It's a big pain because there are two ways to upload, and neither one works for us. We can't use 'setup.py upload' because we don't use 'sdist' to produce our tarball releases (although a discussion of why 'sdist' is insufficient is a topic for another post). The other way to upload, manually interacting with a form in a web browser, is annoying and as far as I know it is hostile to automation.</div><div><br></div><div>Nobody cares because you can 'easy_install twisted' already, and you can find Twisted on the PyPI web page. It's not clear to us what benefits uploading to PyPI would have beyond that.</div><div><br></div><div>If someone would like to give us a good reason to upload or explain how uploading might be made easy, maybe we'd start doing it :).</div></body></html>