Log file Viewer

[19:12:17] <lumidee> hi, why does `python setup.py install` install packages to /usr/lib/python3.5/site-packages/<package_name>-<version>-py3.5.egg/<package_name>/ and not /usr/lib/python3.5/site-packages/<package_name>. installing from pip installs to /usr/lib/python3.5/site-packages/<package_name>

[19:39:04] <lumidee> seems pip doesn't use distutils.commands.install (https://bitbucket.org/carljm/python-distutils/src/48c42eeaee4410d76675b637bcd401b8919ff19a/command/install.py?at=default&fileviewer=file-view-default), but its own install implementation (https://github.com/pypa/pip/blob/develop/pip/commands/install.py) with the difference (assumption) that directories are differently named and ordered in system-packages.

[20:16:31] <ionelmc> lumidee: not really, pip still uses setup.py install - it just adds lots of obscure options to avoid the "egg" installs

[20:17:09] <ionelmc> at least that's how it was till wheels were used internally

[20:17:22] <ionelmc> still works like that if wheel fails to build tho

[20:22:30] <lumidee> good to know, thank you

[21:00:33] <nanonyme> ionelmc, what do you mean by "fails to build"?

[21:03:10] <ionelmc> nanonyme: it fallsback on sdist install (setup.py install) if it fails to build the wheel (bdist_wheel)

[21:03:23] <ionelmc> the wheel caching thing is introduced in 7.0

[21:04:07] <nanonyme> ionelmc, right, so this is about creating the wheel package?

[21:05:02] <ionelmc> nanonyme: not sure what you mean