pmxbot IRC Log Viewer

[00:36:01] <suz> I have an Anaconda installation on Mac OS X 10.8 that I've been using for a couple of months. It's been fine. Now I want to install virtualenv. I downloaded version 1.9.1 (as recommended by my 'Flask Web Development' book) using curl, unpacked it, and ran 'python virtualenv-1.9.1/virtualenv proj1_env'. Unfortunately, I got a long error message that I can't really sort out.

[00:36:50] <glyph> dstufft: what the heck, man: https://asciinema.org/a/8692

[00:36:51] <glyph> what the heck.

[00:36:56] <suz> It gets as far as 'installing setuptools…..' then I get a long teaceback

[00:40:44] <dstufft> glyph: distutils is real bad, do you have a ~/.pydistutils.cfg or a distutils.cfg in the same folder as distutils.__init__.py

[00:41:00] <dstufft> suz: you're going to need to paste the traceback into a pastebin

[00:41:10] <suz> only it's actually a traceback, and seems to fail on: File "/Users/suz/programming/python/webenv/lib/python2.7/sre_constants.py", line 18, in <module>

[00:41:10] <suz> from _sre import MAXREPEAT

[00:41:11] <suz> ImportError: cannot import name MAXREPEAT

[00:41:58] <glyph> dstufft: no.

[00:42:07] <dstufft> glyph: is that Homebrew?

[00:42:09] <glyph> dstufft: This works fine with regular; it doesn't work with python 3.

[00:42:12] <glyph> Yes, it's homebrew

[00:42:16] <glyph> How else could I get python 3?

[00:43:32] <suz> ok. here's the error http://pastebin.com/2siY6feY

[00:43:50] <dstufft> glyph: cuz my Homebrew has a distutils.cfg in the distutils folder

[00:44:08] <suz> might be something to do with older versions, bad path settings…

[00:44:18] <glyph> dstufft: okay you are going to have to imagine something right now

[00:44:39] <glyph> dstufft: just imagine me staring at you really hard, and there's a vein in my forehead, and it's visibly pulsing, and I'm vibrating a little bit, and my eyes are open as wide as they will go

[00:44:49] <glyph> dstufft: that is all

[00:45:16] <dstufft> glyph: I'm not trying to be unhelpful :| I'm trying to make sure that I sort out the cause properly :|

[00:45:25] <glyph> dstufft: Oh, I'm not mad at _you)_

[00:45:42] <glyph> dstufft: just "why does everyone involved have to make this problem even worse"

[00:45:48] <glyph> dstufft: you're probably right about the cause.

[00:46:28] <glyph> The real problem here is that virtualenvwrapper no longer honors VIRTUALENVWRAPPER_HOOK_DIR on python 3. In fact the entire hook structure when you do -p python3 seems to be completely different, and possibly also completely undocumented?

[00:46:29] <glyph> good times.

[00:46:48] <glyph> just more of the quality python3 runtime experience

[00:49:47] <suz> OMG. I got my problems, but at least I'm not bursting a vein with the python3 experience.

[00:49:50] <dstufft> suz: I'm not sure, I don't see anything ther that would cause that, and I don't have an anaconda install handy to repreoduce it

[00:50:24] <dstufft> glyph: that might change if you do -ppython3 instead of -p python

[00:50:45] <dstufft> and if that's the case, you're going to hate the reason why

[00:52:12] <dstufft> glyph: but yea, homebrew sets the prefix option in it's distutils.cfg, and distutils doesn't let you use that with --user, probably we should tell distutils to fuck off and take control of the isntallation more

[00:52:58] <glyph> dstufft: wait _what_

[00:53:10] <dstufft> _what_ to which part

[00:53:32] <glyph> dstufft: oh I thought you meant the hook structure would be the same

[00:53:38] <glyph> dstufft: no, that didn't fix it

[00:53:54] <dstufft> glyph: oh, then it's not a symptom of another problem I've noticed with virtualenvwrapper :/

[00:53:56] <dstufft> sorry

[00:53:59] <dstufft> thought maybe it was

[00:54:08] <glyph> dstufft: no problem, thanks for your help troubleshooting

[00:56:06] <suz> Thanks for looking. I'll see if I can get some local help on Monday or ask on SO. There's already a nice long list of install / virtualenv questions over there….

[03:17:26] <truedon> I am trying to install Cryptography on Mac OSX and I keep getting this error cffi.ffiplatform.VerificationError: CompileError: command 'llvm-gcc-4.2' failed with exit status 1

[03:20:41] <Alex_Gaynor> truedon: I believe https://github.com/pyca/cryptography/issues/834 describes your issue, and there's a workaround in one of the comments

[03:20:55] <Alex_Gaynor> truedon: If you paste teh full traceback I can make sure it's teh same issue though

[03:21:10] <truedon> Alex_Gaynor: ok mate nice one, paste where?

[03:21:28] <Alex_Gaynor> The one in the topc (dpaste.de) works well enough

[03:22:17] <truedon> Alex_Gaynor: ah here http://pastebin.com/imRrQxWi

[03:22:46] <Alex_Gaynor> truedon: what version of OS X do you have?

[03:22:56] <truedon> Alex_Gaynor: 10.7.5

[03:24:53] <truedon> Alex_Gaynor: the solutions there didn't fix it yet

[03:24:58] <Alex_Gaynor> truedon: can you try doing `pip install cryptography>=0.3`, and then redo the scapy command?

[03:25:09] <truedon> Alex_Gaynor: sure thing

[03:25:12] <Alex_Gaynor> It looks like you're getting cryptography 0.2, which doesn't support OS X 10.7.5, we added that back in 0.3

[03:25:43] <truedon> Alex_Gaynor: ah yeh, 0.3 has gone on no problems now. But now install scrappy still fails

[03:25:53] <truedon> because scrappy is trying to get 0.2 version of cryptograph

[03:26:10] <Alex_Gaynor> It says it's trying to get >=0.2.1, why doesn't 0.3 satisfy that :/

[03:26:12] <Alex_Gaynor> cc: dstufft

[03:26:18] <truedon> Alex_Gaynor: strange

[03:29:28] <Alex_Gaynor> truedon: I'm not sure what to tell you, other than this looks like somehow it's a pip bug that it's trying to instlal the oolder version, even after you get the newer one :/

[03:30:27] <truedon> Alex_Gaynor: so how can I get around this, I need to install Scrapy

[03:30:51] <reaperhulk> What version of pip are you running truedon? I'm trying to replicate here and haven't been able to

[03:31:16] <truedon> reaperhulk: I'm on pip 1.1

[03:31:29] <Alex_Gaynor> Can you try installing a new pip (pip install -U pip)?

[03:31:38] <truedon> Alex_Gaynor: sure thing

[03:33:24] <truedon> Updated pip, tried to install scrappy again and it fails on same error with cryptography

[03:33:36] <truedon> I have pip 1.5.4 now

[03:34:03] <reaperhulk> In a clean venv with pip 1.5.4? :/

[03:34:51] <truedon> reaperhulk: yeh I updated in a clean venv, now checking the cryptography is installed with pip list and it doesn't show in the list...

[03:35:05] <Alex_Gaynor> I think we need dstufft for this :/

[03:35:12] <truedon> so looks like cryptography>=0.3 wasn't working an just exiting silently

[03:35:29] <reaperhulk> Yeah I'm out of my depth. Only other thing I could think to ask is what setuptools are you running

[03:35:36] <reaperhulk> That might be worth an upgrade

[03:35:55] <truedon> pip install -U setuptools ?

[03:36:03] <reaperhulk> tell me what version first :)

[03:36:21] <truedon> 0.6c11

[03:36:29] <reaperhulk> yeah go ahead and do that then

[03:36:39] <reaperhulk> should pull down 3.4.1

[03:37:25] <truedon> I get a weird new error when I try to put cryptography on now, check this

[03:37:56] <truedon> http://pastebin.com/DLbB2ZHR

[03:40:01] <reaperhulk> So it's downloading the right package now but not invoking setuptools properly

[03:40:20] <truedon> reaperhulk: yeh

[03:41:12] <truedon> reaperhulk: so how to make it invoke setup tools properly..

[03:41:27] <reaperhulk> Not sure unfortunately :/ never seen this sort of behavior before

[03:41:32] <reaperhulk> what virtualenv are you running?

[03:41:57] <reaperhulk> but 1.11.4 is latest

[03:42:34] <truedon> virtual env 1.7.1.2 i'll update that

[03:49:09] <truedon> hmm do I have to update in brew or something, it seems all of pip is out of date.

[03:49:11] <truedon> So strange

[03:50:25] <reaperhulk> well based on your error output you're using system python, so brew isn't involved here

[03:51:06] <truedon> reaperhulk: ah right… how can I update my venv, pip etc system wide?

[03:52:45] <reaperhulk> What do you get when you type "which pip"

[03:53:14] <reaperhulk> outside of a venv

[04:23:45] <truedon> PIP is in /usr/local/bin/pip

[04:25:53] <Ivo> truedon: sudo pip install -U pip && sudo pip uninstall -y setuptools distribute & sudo pip install -U setuptools & sudo pip install -U virtualenv

[04:28:20] <truedon> I just run that but still when I start a new virtualenv its the older version

[04:29:42] <Ivo> truedon: which virtualenv && virtualenv --version

[04:30:04] <Ivo> maybe not &&, but could you report what those two output

[04:30:16] <truedon> 1.7.1.2

[04:30:31] <truedon> and a path /Users/me/.local/bin/virtualenv

[04:30:38] <Ivo> aha

[04:30:42] <Ivo> theres your problem

[04:31:20] <Ivo> I think that's from a --user install

[04:38:02] <Ivo> truedon: could you check what package directories are in ~/.local/lib/python2.7/site-packages ?

[05:42:25] <glyph> okay now I've got another adventure

[05:45:00] <glyph> setuptools doesn't think it's installed

[05:45:11] <glyph> okay nevermind I'm just going to blow away ~/Library/Python and build this all from scratch again

[06:31:34] <glyph> god damnit everything is broken

[06:31:48] <glyph> new version of virtualenvwrapper changed the way hooks work with no notification (this isn't just python 3)

[06:31:55] <glyph> new version of pip can't import new setuptools any more

[06:32:00] <glyph> new easy-install can't fix it any more

[06:40:10] <glyph> wait no... virtualenvwrapper isn't new, it's just not running my hooks any more (!??)

[06:41:35] <truedon> Ivo: I've got virtualenv 1.7..1.2 and setup tools

[06:42:57] <Ivo> truedon: in ~/.local/lib/python2.7/site-packages ?

[06:43:11] <truedon> Ivo: yeh

[06:44:52] <truedon> Ivo: Shall I just start over, reinstall everything?

[06:46:08] <Ivo> truedon: I'd try sudo pip uninstall virtualenv -y && pip uninstall virtualenv -y

[06:46:45] <Ivo> truedon: hopefully that would uninstall all the copies of virtualenv you have, and then after reinstalling it should work fine

[06:47:04] <Ivo> you could check by seeing if it disaapeasrs from thast folder after

[06:47:32] <truedon> Ivo: Cannot uninstall requirement virtualenv, not installed

[06:48:08] <Ivo> is it still in the .local lib?

[06:48:48] <truedon> Ivo: yeh

[06:48:52] <truedon> Ivo: hasn't changed it

[06:49:20] <Ivo> bah, might need to file a bug for pip; it should be able to uninstall it

[06:50:04] <Ivo> truedon: anyway, you should just be able to delete its folder(s) from site packages, and the relevant scripts in ~/.local/bin

[06:50:22] <truedon> Ivo: ok gonna do that manually now then

[06:50:35] <Ivo> after that your shell will find the one in /usr/bin/ instead

[06:51:17] <truedon> I've removed virtualenv and virtualenvwrapper shall I remove the virtualenvwrapper.sh and virtualenvwrapper_lazy.sh ?

[06:51:52] <Ivo> ya, although virtualenvwrapper is a separate python package from virtualenv

[06:51:52] <truedon> Ivo: yeh I got 1.11.4 now

[06:52:25] <truedon> Ivo: ok I got virtualenv 1.11.4 and pip .1.5.4 now

[06:57:00] <truedon> Ivo: yeh mate all working good now :)

[06:57:31] <Ivo> pip list should tell u the packages and their versions

[06:57:36] <Ivo> you have installed

[06:57:40] <truedon> Ivo: yeh owrking now

[07:07:33] <Ivo> awesome

[10:46:02] <ronny> dstufft: is there any way to install wheels/packages into a custom named directory instead of the normal python prefix/virtualenv - im trying to figure a way to have soemthign like a folder full of eggs, and a pth in the virtualenv

[10:48:26] <glyph> ronny: just unzip them

[10:48:42] <glyph> hmm

[10:48:44] <glyph> maybe 'wheel install' should do that

[11:28:26] <ronny> glyph: im looking for something i dont have to make too much ^^

[11:44:20] <ronny> anyone aware of docs for unit/integration testing setuptools extensions?

[21:32:05] <ronny> jaraco, dstufft: are there any oppinions on having directly importable wheels?

[21:37:02] <jaraco> ronny, I do not yet have any opinion.

[21:40:29] <ronny> hmk

[21:41:04] <ronny> jaraco: im pondering having something where i put multiple verisons of packages int oa direcory, then just have venvs refer to specific files for their imports

[21:41:51] <jaraco> sounds a lot like multi-installed eggs

[21:42:08] <jaraco> I imagine that would be useful.

[21:42:23] <ronny> jaraco: yeah, expect i dont wnat a dynamic/smart workingset, i jsut want a repo, and refer to specific packages in a specific env

[21:43:54] <jaraco> I don't grasp the distinction.

[21:44:36] <ronny> jaraco: with pkg_resources the workingset was dtnamically configurable including multiple versions for a python

[21:44:41] <ronny> i dont want that

[21:44:52] <ronny> instead each env gets exactly only what it refers so

[21:45:29] <jaraco> so you want per-env resolution of packages, instead of per-process?

[21:45:55] <ronny> its not really resolution if there is a pth file refering to exact versions

[21:46:16] <dstufft> tchincally wheels are importable

[21:46:18] <dstufft> I think it's a bad idea.

[21:47:41] <ronny> dstufft: why?

[21:50:10] <ronny> dstufft: in my inderstanding it doesnt matter that much where a package is imported from as long as the set of packages per env cant change without user intervention

[21:50:30] <dstufft> ronny: because a signifcant portion of Wheels just won't work that way

[21:50:45] <dstufft> because they have C exts or because they use __file__ consructs

[21:51:24] <ronny> dstufft: well, im fine with them requiring a extra option which declares them importable

[21:53:07] <ronny> dstufft: and the unsafe ones could just be extracted to the repository instead of being stored there as whl

[21:55:55] <ronny> dstufft: but for stuff like a setup_requires those could be ideal

[21:56:05] <ronny> same goes for webapp deployments

Log file Viewer

Help | Karma | Search:

#pypa logs for Sunday the 6th of April, 2014