pmxbot IRC Log Viewer

[00:49:16] <srid> i noticed that setuptools' `fetch_distribution` completed stopped working; so thought i may just switch pip.

[00:49:22] <srid> but so far my attempts have failed

[00:49:24] <srid> https://gist.github.com/srid/3ce8762e7e4b1f7b17b9

[00:49:51] <srid> uses `finder.find_requirements` (among other stub); but it throws DistributionNotFound

[00:49:54] <srid> what am i doing wrong?

[00:59:04] <dstufft> srid: you're not giving it any urls to locate at

[00:59:46] <dstufft> try finder = PackageFinder([https://pypi.python.org/simple/], [], session=session)

[00:59:49] <dstufft> er

[00:59:53] <dstufft> except as a string

[01:02:47] <dstufft> srid: also you can just create your own session object, it's in pip.download.PipSession

[01:04:57] <srid> dstufft: thanks ... now it seemed to work (took a few seconds to run), but still prints "pip.exceptions.DistributionNotFound: No distributions at all found for appdirs"

[01:05:02] <srid> ill try the PipSession thing now

[01:05:37] <Ivo> srid: btw pip doesn't advertise itself as having any stable api

[01:06:16] <srid> hmm

[01:08:11] <Ivo> what's in 1.4/1.5 won't change, but there's too much stuff to improve to make promises about future versions

[01:35:25] <pmxbot> jaraco pushed 1 commit to setuptools (https://bitbucket.org/pypa/setuptools/) :

[01:35:25] <pmxbot> Include the build launcher script in setuptools sdist. This helps address the requirement that all sources be included.

[15:35:04] <qwcode> dstufft, 503 http://packaging.python.org/

[15:35:35] <dstufft> qwcode: i'll take a look in a moment

[15:43:59] <qwcode> dstufft, thanks

[16:51:15] <Ivo> whats going on with packaging.python.org?

[16:58:13] <dstufft> strange

[16:58:14] <dstufft> error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong version number

[18:55:29] <gauravb7090> hey

[18:57:05] <gauravb7090> I just figured out that many packages listed on the https://pypi.python.org/pypi?%3Aaction=index dont have complete info like the download url and description

[18:57:47] <gauravb7090> for instance https://pypi.python.org/pypi/pysheet/0.3.6 --> https://pypi.python.org/pypi/pysheet/0.3.6/json doesnt have a download url

[18:59:48] <gauravb7090> so how does pip does all the installing?

[19:00:07] <gauravb7090> now it uses the xmlrpc api if I'm not wrong?

[19:00:29] <Ivo> the download url is informational only 98% of the time

[19:00:31] <gauravb7090> is there a canonical source of data also present?

[19:01:05] <gauravb7090> so how does it work actually?

[19:01:15] <Ivo> you can see the urls it downloads from in the releases object

[19:02:09] <gauravb7090> then the normal make configure and install approach after downloading?

[19:02:29] <Ivo> whats your end goal asking these questions

[19:02:38] <gauravb7090> what about the additional dependencies if any?

[19:03:35] <Ivo> pip will analyse the package it downloads for dependencies and install those, and then install the package

[19:04:17] <Ivo> if its an sdist it will invoke setuptools to install the package

[19:04:39] <Ivo> it can install a wheel by itself

[19:10:24] <dstufft> gauravb7090: pip looks at https://pypi.python.org/simple/pysheet/

[19:11:24] <gauravb7090> these are for all the releases…these are also listed on the https://pypi.python.org/pypi/pysheet/0.3.6/json

[19:11:44] <gauravb7090> but I wanted to know more about the working of pip like Ivo was telling

[19:11:53] <gauravb7090> it branches on the type of file?

[19:12:03] <gauravb7090> type of info rather

[19:12:06] <Ivo> gauravb7090: doesn't use the json interface yet

[19:13:49] <gauravb7090> Ivo can you please explain in brief how it works?

[19:13:57] <Ivo> how what works

[19:14:13] <gauravb7090> installation of a package

[19:14:36] <Ivo> either it unpacks a wheel or it passes it to setuptools

[19:14:39] <Ivo> to do lots of fun stuff

[19:14:40] <gauravb7090> looking from pypi theres just a simple single download url that dies eveything

[19:14:55] <gauravb7090> does* everything

[19:14:56] <Ivo> gauravb7090: dstufft gave you the url pip actually parses

[19:17:03] <Ivo> gauravb7090: http://warehouse.readthedocs.org/en/latest/api-reference/legacy/ has some limited docs on the api of those urls

[19:20:27] <gauravb7090> okay I'll give them a thorough read and then get back to you if I dont understand anything

[19:20:38] <gauravb7090> thanks Ivo and dstufft :)

[20:12:06] <Ivo> dstufft: giving ppl a pip which updated with python patch version would be so cool if distros hadn't nuked it :(

[20:12:55] <dstufft> Ivo: heh

[20:12:57] <dstufft> it's not all bad

[20:13:15] <dstufft> once the dust settles i'm planning on making repos for pip and virtualenv

[20:13:28] <dstufft> that will replace the pinned distro versions

[20:13:37] <Ivo> actually, no

[20:13:46] <Ivo> that would require them to have 3.4 in the first place...

[20:14:11] <Ivo> did ubuntu 14.04 ship with 3.3?

[20:14:15] <dstufft> yes

[20:14:16] <dstufft> eer

[20:14:17] <dstufft> no

[20:14:19] <dstufft> 3.4

[20:14:37] <Ivo> fucking sweet

[20:15:16] <dstufft> it doesn't ship with ensurepip tho

[20:15:19] <dstufft> because reasons

[20:15:42] <Ivo> is venv borked atm then?

[20:15:50] <Ivo> or they circular dependency pip with python

[20:15:56] <dstufft> it's borked

[20:16:04] <dstufft> python -m venv raises an error by default

[20:16:10] <Ivo> SO CLOSE

[20:16:13] <dstufft> you can do python -m venv --without-pip

[20:16:17] <dstufft> or w/e the flag is

[20:16:30] <Ivo> SO CLOSE TO BEING GOOD

[20:20:10] <Ivo> actually.. a venv created pip should never be a system pip, right?

[20:20:19] <Ivo> so I wonder why distro ppl are all worried about it

[20:22:47] <dstufft> ~policy~

[20:24:39] <Ivo> like the --without-ensurepip module just stops you from using a bundled pip as a system tool, right, it doesn't remove it from being installed into venvs?

[20:24:45] <Ivo> s/module/flag

[20:27:57] <qwcode> dstufft, any luck with 503. should it be a report to someone else?

[20:29:20] <dstufft> Ivo: correct, they also did rm -rf ensurepip

[20:29:25] <dstufft> qwcode: partially done

[20:29:34] <Ivo> what went wrong?

[20:29:58] <dstufft> RTD switched their SSL stuff and it's throwing SSL errors

[20:33:26] <Ivo> man, ppl

[20:34:36] <Ivo> https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1290847/comments/18 I don't get why anyone would want to make so much work for themselves

[20:50:52] <Ivo> if debian has to build things from source wtf does it do with virtualenv

[20:52:28] <Ivo> https://packages.debian.org/sid/all/python-virtualenv/filelist

[21:24:12] <dstufft> they ignore it for virtualenv

[21:24:21] <Ivo> which is bs

[21:41:34] <xafer> hello, I'm trying to understand the internals of pip and I'm stuck on the "unpack_*" functions:

[21:42:36] <tomprince> Ivo: It probably slipped past them for virtualenv, and they rather address that too.

[21:42:50] <xafer> why is unpack_file dealing with subversion: https://github.com/pypa/pip/blob/develop/pip/util.py#L628 while there exists unpack_vcs_link here: https://github.com/pypa/pip/blob/develop/pip/download.py#L358

[21:43:49] <tomprince> Maybe I dreamed this, but I have a recollection of a distro that has pip and setuptools install the associated virtualenv_support files, and then virtualenv depends on them.

[21:44:04] <Ivo> xafer: probably because it doesn't have a good separation of concerns and could be rewritten

[21:46:34] <xafer> Ivo, that's what I'm wondering. Because it seems that unpack_file do accept html files containing info on a subversion repo: is it really an usecase ??

[21:51:21] <Ivo> tomprince: well if they want to go through the pain of rewriting vendoring scripts for the sake of not having zips of source code then I want to make sure they're not skimping out on it

[21:52:50] <dstufft> they aren't doing that exactly anymore

[21:53:02] <dstufft> they are doing something equally as janky but differently so

Log file Viewer

Help | Karma | Search:

#pypa-dev logs for Thursday the 22nd of May, 2014