pmxbot IRC Log Viewer

[00:24:01] <msabramo> still doing 6.0.x releases for pip?

[00:26:31] <dstufft> msabramo: probably yea

[00:27:06] <msabramo> oh well

[01:25:19] <ionelmc> dstufft: hmmm, changelog is not updated?

[01:25:37] <dstufft> ionelmc: I didn't push it yet

[01:26:02] <dstufft> I'm merging 6.0.3 into virtualenv fist because the pip push will tie up our travis builders for awhile

[06:36:16] <Ivo> dstufft: what stuff borked in virtualenv for the syspath changes?

[07:09:43] <Ivo> dstufft: also I totally should have mentioned that we really needed to do a beta release of the next virtualenv major

[07:10:34] <Ivo> just upgrading setuptools/pip in a 1.11.7 or smth would been a little easier :P

[16:35:27] <msabramo> $ easy_install pip==6.0.2

[16:35:28] <msabramo> Searching for pip==6.0.2

[16:35:28] <msabramo> Reading https://pypi.python.org/simple/pip/

[16:35:28] <msabramo> /Users/marca/python/virtualenvs/pip/lib/python2.7/site-packages/pkg_resources.py:2443: PEP440Warning: 'pip (dev)' is being parsed as a legacy, non PEP 440, version. You may find odd behavior and sort order. In particular it will be sorted as less than 0.0. It is recommend to migrate to PEP 440 compatible versions.

[16:35:28] <msabramo> PEP440Warning,

[16:35:46] <msabramo> 'pip (dev)" — kind of weird

[16:43:28] <sigmavirus24> "pip (~~~dev~~~)" better ;)

[17:07:49] <msabramo> hmmm virtualenv not copying modules seems to happen with every new python version

[17:08:05] <msabramo> maybe Python needs to have an "API" where it provides a list of modules that should be copied?

[17:08:19] <dstufft> the real answer is venv

[17:08:32] <dstufft> virtualenv needs to get out of the isolation game, let the interpreter handle it

[17:13:27] <msabramo> I always forget about venv; old habits die hard

[17:48:51] <dstufft> trying out pyramid

[17:48:56] <dstufft> getting mad at the ini files

[17:51:36] <sigmavirus24> lmao

[17:51:52] <dstufft> I'm pretty sure I'm never going to be happy with a web framework

[17:51:54] <dstufft> ever

[17:52:13] <sigmavirus24> s/web framework/software/

[17:52:15] <dstufft> I wish I could go back to when I thought django was the best thing that was ever created

[17:52:26] <sigmavirus24> You can never go back

[17:52:30] <sigmavirus24> I've tried

[17:52:30] <dstufft> I was so young and full of hope

[17:52:31] <dstufft> I was also an idioot

[17:52:33] <dstufft> idiot

[17:52:34] <sigmavirus24> lmao

[17:52:44] <sigmavirus24> This is better suited for #yolomad =P

[19:36:07] <ionelmc> dstufft: does the new pip use coloring in output?

[19:36:24] <dstufft> yea, same as 1.5

[19:36:37] <ionelmc> cause on windows it just outputs the raw escape sequences, eg: ←[K 100% |################################| 1.8MB 1.1MB/s ta 0:00:011

[19:37:23] <ionelmc> wondering if there's something wrong

[19:37:34] <dstufft> on windows we use colorama to color the output

[19:37:52] <dstufft> I didn't even know the progress bars worked on windows heh

[19:40:20] <ionelmc> weird

[19:40:29] <ionelmc> dstufft: but it vendors colorama rirght?

[19:40:39] <dstufft> yes

[19:41:40] <ionelmc> dstufft: have you seen anything like this

[19:41:43] <ionelmc> https://www.irccloud.com/pastebin/nHnmZ1hY

[19:42:03] <dstufft> yea, there's an open ticket about it

[19:42:13] <ionelmc> any workaround?

[19:42:46] <dstufft> dunno :/ It's super confusing to me and any attempts to fix it seem to be breaking more things

[19:42:49] <ionelmc> also, virtualenv's pypi page is raw text

[19:46:44] <ionelmc> dstufft: were you able to reproduce the "virtualenv is not compatible with this system" ?

[19:47:02] <dstufft> which one

[19:47:09] <sigmavirus24> dstufft: weekend project: rewrite virtualenv =P

[19:47:15] <ionelmc> the https://etherpad.openstack.org/p/pydistutils-issues "bug"

[19:47:19] <dstufft> yes

[19:47:21] <ionelmc> if you can call that a but report

[19:47:33] <sigmavirus24> ionelmc: it is a butt report

[19:47:38] <sigmavirus24> I reported it from my butt

[19:47:45] <dstufft> ionelmc: that wasn't a bug report, that was them talking to me in IRC and using that to send me details

[19:47:59] <dstufft> I just pasted it becuase I was tired and frustrated and angry

[19:48:01] <dstufft> and didn't feellike writing more

[19:48:05] <dstufft> sigmavirus24: I'm considering it

[19:48:21] <ionelmc> terrible :)

[19:48:34] <sigmavirus24> dstufft: I wish I had a better understanding of everything virtualenv has to do to work

[19:49:12] <dstufft> I wish anyone had an understanding of what virtualenv is doing

[19:49:15] <dstufft> I half understand it

[19:49:21] <dstufft> at a high level

[19:49:46] <collinanderson> dstufft: I'm interested in meeting up with Ian Bicking at some point. Anything I should ask? :)

[19:49:59] <sigmavirus24> collinanderson: why he hates us ;)

[19:50:13] <sigmavirus24> (me is totally being facetious)

[19:51:16] <collinanderson> completely changed how install packages in python, and left :)

[19:51:25] <collinanderson> *people install

[19:52:44] <dstufft> maybe I'll workon virtualenv2 instead of getting mad at the wev

[19:52:45] <dstufft> web

[19:53:07] <ionelmc> mad at virtualenv then?

[19:53:15] <dstufft> always mad at something

[19:53:25] <dstufft> that's just a given for me

[19:53:51] <sigmavirus24> dstufft: same here

[19:54:00] <sigmavirus24> It wouldn't be a day in the life if I werent' angry at something

[19:57:27] <collinanderson> dstufft: call it something shorter. venv2

[19:57:54] <collinanderson> dstufft: i don't like typing long things

[19:58:06] <dstufft> collinanderson: alias it to v

[19:58:08] <dstufft> :D

[19:58:17] <collinanderson> dstufft: perfect. pyv is also ok

[19:58:27] <ionelmc> collinanderson: it needs to be longer, you have to suffer a bit to use it, cause dstufft is gonna suffer a lot to implement it hehehe

[19:58:38] <Alex_Gaynor> dstufft: this mean you're not going to write the pep

[19:58:40] <sigmavirus24> ionelmc: A+ reasoning

[19:58:54] <sigmavirus24> dstufft: let me know how I can help too

[19:59:10] <dstufft> Alex_Gaynor: no, I'm going to write the pep

[19:59:26] <collinanderson> dstufft: ohh, and rip off npm is possible. make it so you can create a venv and install packages in one step

[19:59:26] <dstufft> Alex_Gaynor: long term virtualenv is going to be a frontend for the venv module

[19:59:39] <sigmavirus24> collinanderson: feature creep. /ban collinanderson

[19:59:42] <collinanderson> :)

[19:59:50] <dstufft> that does things like "let me upgrade the copy of setuptools/pip that get installed by default" andother UX centric things

[19:59:59] <ionelmc> collinanderson: *cough*, pip had *that* feature

[20:00:03] <ionelmc> but it was removed

[20:00:22] <sigmavirus24> ionelmc: don't be bitter. that doesn't sound like something that belonged in pip

[20:00:50] <sigmavirus24> You all realize tox does this for you, right? Create virtualenv -> install deps

[20:00:53] <dstufft> it was removed because the way it was implemented was broken as heck

[20:01:00] <collinanderson> seems like a useful feature to me. i might even consider using venvs more rather than symlinking libraries :)

[20:01:02] <ionelmc> sigmavirus24: but it made me blissfully ignorant!

[20:01:21] <sigmavirus24> ionelmc: ignorance is only a footgun. never bliss

[20:01:22] <sigmavirus24> ;)

[20:01:30] <ionelmc> well, i'm over the removal now

[20:01:36] <collinanderson> sigmavirus24: yeah, i was just thinking about that (tox).

[20:01:40] <sigmavirus24> took you long enough ionelmc =P

[20:01:53] <sigmavirus24> collinanderson: add a tox env "int" for interpreter and boom

[20:01:55] <ionelmc> it was very depressing!

[20:02:05] <ionelmc> features are like kittens

[20:02:11] <sigmavirus24> ionelmc: it's software. just fork, release and move on =P

[20:02:12] <ionelmc> you don't like to kill kittens do you

[20:02:20] <sigmavirus24> ionelmc: I LOVE killing kittens /snark

[20:02:30] <ionelmc> hahahah

[20:02:42] <sigmavirus24> why else would I keep so many cat people around?

[20:02:51] <sigmavirus24> they all have kittens I can slaughter

[20:23:54] <ionelmc> damn it bug is really weird

[20:24:11] <ionelmc> dstufft: looks like virtualenv runs itself with the target interpreter

[20:25:02] <ionelmc> when it runs with python3.4 it has C:\Python27\lib\site-packages in the sys.path

[20:25:33] <ionelmc> dstufft: so i'm looking at the env vars and there's no PYTHONHOME set: https://gist.github.com/ionelmc/519383d114559993057b

[20:25:40] <ionelmc> i don't get it :-|

[20:28:01] <ionelmc> any clues?

[21:23:59] <ionelmc> dstufft: seems to work fine with https://github.com/mgedmin/virtualenv/commit/eabbdec009e90ba40bafb31305a80b5048f5dcb0 - any idea what happen with that commit?

[21:47:16] <pmxbot> jaraco pushed 1 commit to setuptools (https://bitbucket.org/pypa/setuptools/) :

[21:47:16] <pmxbot> Add test making explicit the expectation that pkg_resources shouldn't import setuptools (or be dependent on it in any way). Ref #311.

[22:03:56] <pmxbot> jaraco pushed 2 commits to setuptools (https://bitbucket.org/pypa/setuptools/) :

[22:03:56] <pmxbot> Moved pkg_resources into its own package.

[22:03:56] <pmxbot> Move vendored packaging module into pkg_resources._vendor, restoring independence of pkg_resources from setuptools. Fixes #311.

[22:12:17] <msabramo> oh wow, pkg_resources separated form setuptools

[22:12:42] <dstufft> it's own import package, not distribution package

[22:26:15] <pmxbot> jaraco pushed 5 commits to setuptools (https://bitbucket.org/pypa/setuptools/) :

[22:26:15] <pmxbot> Setuptools now uses the 'packaging' package from pkg_resources, unifying the behavior around resolution of that package.

[22:26:15] <pmxbot> Update changelog

[22:26:15] <pmxbot> Bumped to 8.3 in preparation for next release.

[22:26:15] <pmxbot> Added tag 8.3 for changeset cd14b2a72e51

[22:26:15] <pmxbot> Bumped to 8.4 in preparation for next release.

Log file Viewer

Help | Karma | Search:

#pypa-dev logs for Wednesday the 24th of December, 2014