On Thu, Mar 20, 2008 at 12:17 AM, Jeff Rush <[EMAIL PROTECTED]> wrote:
[cut] > - move to https/ssl > Semi-related: There are a few problems in this area, also related to indexing we need to work out imho: When a package defines a https://... link into the url meta-data, the link will be added in the Simple index besides other links. For instance, people that uses sourceforge can have such urls. Even if the package egg or tarball is available at PyPI, the home page url will appear at #1 on the index page. This will make tools like easy_install read this link before it reaches the egg/tarball. This is OK as long as the users behind the firewalls are allowed to call htppS... so that's a PyPI server *and/or* setuptools issue > [cut] > - some auto-generated reports of access statistics and the mix > of distutils vs setuptools, those who "registered" w/o > "uploading", and perhaps if we get a new classifier assigned, > some idea of Python 2.x vs 3.x packages. > In this area, I have proposed a few months ago to make the classifiers permissive see http://wiki.python.org/moin/EnhancedPyPI. Just wanted to say again, that this work is in my pile for turning PyPI errors into warnings when a classifier is unknown. The last thing I wanted to express in the state of packaging is that it took me a long time to understand where all pieces of code belonged to, between distutils and setuptools. I have found some bugs in distutils, and did add some issues, patches, and discovered after that setuptools had them resolved in its code. I am feeling very frustrated on this because the boundary between the two package is very fuzzy. Maybe this is just a doc issue. In the meantime, I might be naive but I don't really understand why some part of setuptools are not merged into distutils, when it does the same things, but in a more robust way. Cheers Tarek
_______________________________________________ Distutils-SIG maillist - [email protected] http://mail.python.org/mailman/listinfo/distutils-sig
