On 2015-04-22 19:47, Artur Wroblewski wrote: > On Wed, Apr 22, 2015 at 6:38 PM, Jacek Konieczny <jaj...@jajcus.net> wrote: >> On 2015-04-22 17:41, Elan Ruusamäe wrote: >> In the meantime another project 'distutils2' was announced, which was to >> supersed both setuptools and distribute, but that didn't really happen. >> Instead, 'distribute' was merged back to 'setuptools' and 'setuptools' >> is what the world uses now. > > Also, pip is the blessed way of installing the modules now, see > > https://www.python.org/dev/peps/pep-0453/#abstract
Yeah… blessed by developers, who don't care about system consistency etc. Installing packages with pip doesn't go well with providing consistent Linux distribution packages. We could probably minimize the damages pip can do by making it somehow install 'system-wide' packages to /usr/local instead of /usr… but that would probably require changes in our Python packages and can cause new compatibility problems. Currently our pip installs packages into /usr/share/site-packages, overwirtting whatever is already there (from PLD RPM packages) making a real mess of the system. Additionally our pip is stipped of the private copies of some libraries it uses (requests, urllib2), which are sometimes used by other python packages. Yes, Python developers went the Java way – „instead of creating stable interfaces, let's just redistribute random version of all required libraries with our software. Or ask to use virtualenv for everything. Twenty copies of ten different versions of 'requests'? What could go wrong? Like, if a security problem was found… Jacek _______________________________________________ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en