Rationalizing Python packaging

Posted Oct 16, 2013 21:27 UTC (Wed) by Tobu (subscriber, #24111)
Parent article: Rationalizing Python packaging

Here is a good place to profess my love of pip, and particularly the way it has unified the mess by focusing on source packages. No leaky restrictions from intermediate formats, and if something needs to be fixed, the user sees exactly what the developer sees.

I haven't followed this completely; I assume the plan is to keep the user-visible parts of setuptools hidden for their eventual deprecation? Because I really don't want people to learn or try to “fix” easy_install whenever it turns out to be broken (or break other things, like the search path).