pmxbot IRC Log Viewer

[00:09:32] <noink> hi there, I have a problem installing pysqlite for python 3.4.2

[00:09:54] <noink> pip exits with error

[00:09:55] <noink> File "/tmp/pip_build_root/pysqlite/setup.py", line 85

[00:09:55] <noink> print "Is sphinx installed? If not, try 'sudo easy_install sphinx'."

[00:09:55] <noink> ^

[00:09:55] <noink> SyntaxError: Missing parentheses in call to 'print'

[00:10:35] <noink> how come pip doesn't support python3 call ?

[00:16:00] <jrabbit> noink: pysqlite may not support py3

[00:16:11] <jrabbit> that's not pip's fault.

[00:17:54] <noink> ehm, how come

[00:18:13] <noink> sqlite3 not supported by py3 ?

[00:18:54] <jrabbit> I have no clue but that traceback is a problem with pysqlite

[00:29:55] <noink> jrabbit> you are right, still, I can't find any solution for the problem

[00:45:00] <buck1> is there a function to check if a particular pkg==version wheel exists in a wheelhouse?

[00:59:56] <buck1> is pip.commands.wheel using pkg_resources rather than pip._vendor.pkg_resources for some good reason?

[01:02:32] <buck1> !log

[07:11:32] <mgedmin> what was the pep that bundled setuptools with python 3.4?

[07:44:47] <dstufft> 453

[07:56:42] <mgedmin> thanks

[07:57:05] <mgedmin> fun story: zc.buildout really really wants to have a system python without setuptools for its own test suite

[07:57:23] <mgedmin> it goes to great lengths to download a pristine python tarball from upstream and build it locally, just to run its tests

[07:57:34] <mgedmin> and now python 3.4 comes and installs setuptools in its pristine site-packages hehehe

[07:57:45] <mgedmin> anyway ./configure --without-ensurepip makes buildout's silly test suite happy

[11:18:20] <techtonik> pypa turns into monolith that will be embedded in interpreter pgp way =)

[12:30:26] <dAnjou> hi, can i include other configuration files in $HOME/.pip/pip.conf?

[12:32:21] <apollo13> you can't afaik

[12:50:36] <dAnjou> meh :/

[12:50:54] <dAnjou> that makes config management really hard

[12:51:03] <doismellburning> dAnjou: yes!

[12:51:14] <dAnjou> what yes?

[12:51:25] <doismellburning> dAnjou: yes it does make it hard

[12:51:31] <dAnjou> ah

[12:52:53] <mgedmin> you could also configure your pip by setting PIP_xxx environment variables in your ~/.bashrc (or files sourced from it)

[12:57:27] <dAnjou> hmm, that seems more of a hassle than modifing the file

[13:04:50] <dAnjou> good enough and it's packaged in ubuntu/debian http://www.pixelbeat.org/programs/crudini/

[16:30:59] <straycat> Given http://sprunge.us/DNcM , should I take it that pip will error if there's a dependency conflict?

[17:54:49] <nanonyme> mgedmin, you could make your ~/.bashrc source ~/.pip/pip.conf

[17:54:59] <nanonyme> Oh, dAnjou. Anyway

[17:55:44] <nanonyme> Although I suspect you want ~/.bash_profile, not ~/.bashrc

[17:56:01] <mgedmin> nanonyme, that sounds like an incredibly bad idea!

[17:56:11] <nanonyme> Otherwise your settings will be reloaded on every sub-shell

[17:56:13] <mgedmin> pip.conf is an INI file, not a shell script!

[17:56:20] <nanonyme> Oh, never mind :P

[17:56:52] <nanonyme> My point was, you can make the ~/.bash_profile load from other files making maintenance less of a hassle

[17:57:01] <mgedmin> yeah

[18:20:12] <josePhoenix> Hi all

[18:20:24] <josePhoenix> Is there any way to host multiple versions of documentation on PyPI?

[18:20:32] <josePhoenix> e.g. with pythonhosted.org

[18:23:40] <doismellburning> josePhoenix: readthedocs.org ?

[18:23:58] <josePhoenix> Won't build my package, alas

[18:26:02] <josePhoenix> (well, it'll claim to install numpy into the virtualenv, but it doesn't appear to be available when they run setup.py for my package)

[20:20:48] <solaries> hi all

[20:22:11] <solaries> pip installing python-twitter in a py3 virtualenv gives an exception because it fetches simplejson which is not py3-compliant

[20:22:11] <solaries> any idea how to force some simplejson alternative?

[20:32:09] <tomprince> If it has dependencies that aren't python3 compatible, then it probably isn't python3 compatible itself.

[21:23:51] <Yasumoto> yeah, you could send a patch to either simplejson (for py3 compatibility) or python-twitter to use something else

[21:25:25] <doismellburning> I can't help but note https://github.com/simplejson/simplejson/blob/master/setup.py#L31-L33

[21:26:29] <doismellburning> solaries: by `python-twitter` dym https://pypi.python.org/pypi/twitter ?

[21:26:44] <doismellburning> guess not, it lists py3s

[21:27:27] <doismellburning> ah, https://pypi.python.org/pypi/python-twitter/2.0

[21:27:32] <doismellburning> which lists 3.3 support

[21:29:18] <doismellburning> and https://github.com/bear/python-twitter/blob/v2.0/setup.py#L41 which doesn't include simplejson

[21:29:30] <doismellburning> solaries: so yeah, I'm a little confused

[21:29:36] <doismellburning> more detail please?

[21:31:05] <carljm> doismellburning, solaries: https://github.com/bear/python-twitter/commit/0424031d8cd7770e6a6ffa95fa756760fb6eb0d0

[21:31:14] <carljm> it seems a simplejson dependency was removed in July.

[21:31:46] <carljm> and shortly thereafter version 2.1 was released.

[21:31:49] <carljm> what version are you using?

[21:32:48] <carljm> Hmm, actually it looks like the project's setup.py was bumped to 2.1, but 2.1 was never released to PyPI.

[21:33:24] <carljm> So you could either bug the maintainer about releasing 2.1 to PyPI, or install it from git (or create yourself a 2.1 sdist using 'python setup.py sdist' and install that)

[21:34:59] <doismellburning> carljm: it looks to me like it was removed in 2.0 too...

[21:35:08] <doismellburning> s/was removed/isn't present/

Log file Viewer

Help | Karma | Search:

#pypa logs for Tuesday the 4th of November, 2014