Log file Viewer
#pypa logs for Friday the 19th of June, 2015
[07:12:45] <KlausedSource> hello guys, i have issues with virtualenv/pip on my new ubuntu 14.04 vps. I wanted to install django-cms in a virtual env (everything without sudo). While most modules installed without problems, PIP complains about missing permission on some others.
[07:44:41] <doismellburning> KlausedSource: if you were to gist some actual context (command line, the actual error etc.) then people might be able to help - without more information from you, you're unlikely to get much information back - "it's possible because something's not working right"
[07:50:03] <KlausedSource> doismellburning, i am still trying to figure what the actual problem is. i might have a lead, keeping you updated
[07:51:57] <doismellburning> KlausedSource: right, but you realise you've basically provided no real information about the basics of the _symptoms_?
[07:52:15] <doismellburning> KlausedSource: i.e. only _you_ know the command you ran, and the output you got
[07:52:58] <doismellburning> and there's many ways you could "install a module" (especially if you're not doing it right) and multiple ways I'm sure pip can "complain about missing permission on some others"
[08:10:27] <KlausedSource> doismellburning, yes I am sorry, prob shouldn't have asked. TBH, I am currently not having constant access to the machine and thus can't reproduce the issue right now. Sorry again for bothering you next time I ask will make sure theres enough "evidence".
[08:11:16] <KlausedSource> This was bugging me the whole night yesterday and the first thing that came to my mind was looking for a solution
[08:11:37] <doismellburning> KlausedSource: oh it's no bother, I totally understand that sometimes you _can't_ get that data - it just wasn't clear whether you had problems getting it, or just didn't understand that it'd be helpful
[08:12:31] <doismellburning> KlausedSource: I've spent a bit too much time with people who've sometimes not fully appreciated that, without actual details, it's a bit hard to provide useful help
[13:45:51] <William__> Hi all. I am trying to deploy warehouse, however running 'docker-compose up' throws an exception on camo: "fatal: unable to access 'https://github.com/atmos/camo.git/': server certificate verification failed". How can I resolve this issue?
[15:40:12] <gtback__> Question about wheels: I've got a package "A" where there is an extra dependency for Python 2.6 (weakrefset). Right now I'm only publishing .tar.gz and .zip (I know I should be using wheels, but I don't think that completely solves this particular problem). I'm running Tox to test another package "B" which depends on A. Pip automatically builds and caches
[15:40:12] <gtback__> wheels on install, so if I have existing wheel that was built with Python 2.7, it won't contain the dependency on weakrefset. If I delete the cached wheel and rebuild it with Python 2.6, the wheel knows it needs weakrefset and installs correcdtly. Since the wheel specifier only includes "py2" (it's pure Python), it's sort of a race condition to see whether
[15:40:12] <gtback__> Python 2.6 or Python 2.7 builds and caches the wheel first. I can see a few solutions, but I'm curious which is best?
[15:40:49] <gtback__> - Always build and publish a wheel with Python 2.6 so "weakrefset" will get installed even on Python 2.7 where it isn't necessary.
[15:41:26] <dstufft> if you can mandate you use a recent pip and setuptools you can use the setuptools variant, where you add an extra named uh, :python_version == '2.6'
[15:42:35] <gtback__> dstufft: I've seen those, that was one of my options, but I've been trying to support people needing to use RHEL 6 with as few non-standard packages as possible.
[15:42:52] <dstufft> otherwise if you can't, you do the conditional in setup.py the old way (e.g. progrmatically) and you add a setup.cfg like: https://github.com/pypa/twine/blob/master/setup.cfg#L9-L13 (note this overrides the _entire_ dependency listing inside the wheel so you have to duplicate)
[15:56:57] <gtback__> I think using setup.cfg will work best for me. The duplication is unfortunate, but seems unavoidable since to support both wheels and older versions of pip/setuptools.
[16:03:22] <gtback__> Is there newish documentation about the setup.cfg file? I found https://docs.python.org/2/distutils/configfile.html which is more general, and http://alexis.notmyidea.org/distutils2/setupcfg.html which has more details but is perhaps outdated (still refers to PEP 345 and PEP 386, plus distutils2 is old... though I imagine most of the data is accurate). I
[16:04:08] <gtback__> btw, setuptools.readthedocs.org should probably be removed or redirected to pythonhosted.org/setuptools... it's pretty old ;-)
[22:35:50] <malin1> hi, i registered to pypi and didnt get the confirmation email for some reason (smtpd had issues). now when i try to register a package, it says 401: incomplete registration, check your email. I didnt find a way to have pypi site re-send the registration email. Any idea?