[08:21:12] <ionelmc> i may be looking at old setuptools code tho
[08:21:54] <ionelmc> ah no, it's like that: https://bitbucket.org/pypa/setuptools/src/b6e4e89191a674855e06114e8072f2449ef53347/_markerlib/markers.py?at=default#cl-48
[08:22:52] <mgedmin> https://www.python.org/dev/peps/pep-0426/#environment-markers says there's no dot
[08:23:44] <ionelmc> mgedmin: no idea what's going on there, there i so many peps i go straight to the code when i'm in doubt
[08:37:40] <ionelmc> mgedmin: this is the actual env https://bitbucket.org/pypa/setuptools/src/b6e4e89191a674855e06114e8072f2449ef53347/pkg_resources/__init__.py?at=default#cl-1392
[08:37:52] <ionelmc> looks like _markerlib has deadcode?!
[08:38:26] <ionelmc> i suppose a bug report in setuptools is a good start
[08:39:27] <ionelmc> it would appear it still use markerlib https://bitbucket.org/pypa/setuptools/src/b6e4e89191a674855e06114e8072f2449ef53347/pkg_resources/__init__.py?at=default#cl-1526
[08:42:04] <ionelmc> this is why i dislike dependency bundling, me and plenty of other people expect that the shipped code is not a mixture of copied deadcode
[08:51:01] <mgedmin> pip list --outdated -> bunch of packages, some from ~/.local, some from ubuntu's dist-packages
[08:51:11] <mgedmin> pip list --outdated --user -> only one package (hypothesis)
[08:51:22] <mgedmin> where are all the other outdated user packages go?
[14:26:36] <tomprince> mgedmin: My impression is that PEP-426 isn't fully suppported, now.
[18:24:45] <ronny> tomprince: as far as i understood toosl dont support it propperly atm
[18:27:12] <pandb> can i/should i change permissions to /usr/python/site-packages so that i can use pip without sudo or su every time?
[18:28:10] <ronny> pandb: in general /usr is under the control of the package manager if the linux distribution, you shouldnt put things in it, that the package manager does not handle
[22:43:26] <warner> hi folks.. I'm hacking on Versioneer today (https://github.com/warner/python-versioneer) and had a question
[22:43:43] <warner> is it ever correct to run a setup.py command from outside the package's directory?
[22:43:58] <warner> e.g. something like "python .../path/to/setup.py install"
[22:44:07] <warner> as opposed to "cd .../path/to && python setup.py install"
[22:44:49] <warner> it seems like pip/easy_install tend to run setup.py commands from the same directory as the setup.py, but I'm trying to work out if I need to support running those commands from a different directory