PMXBOT Log file Viewer

Help | Karma | Search:

#pypa logs for Sunday the 25th of May, 2014

(Back to #pypa overview) (Back to channel listing) (Animate logs)
[01:50:03] <agronholm> I didn't realize that wheels can't be arbitrarily named
[01:50:24] <agronholm> their names have to match the spec or pip refuses to install them
[02:27:49] <Ivo> agronholm: I'm not a fan of deriving metadata from filenames either, but it is what it is
[02:28:19] <agronholm> why can't it just look in the metadata inside the zip? should be trivial
[02:28:51] <Ivo> because the PEP specifies that the filename is important
[02:28:57] <agronholm> meh
[02:31:06] <Ivo> agronholm: there is https://github.com/dstufft/peps/blob/master/moar-better-wheels.rst to comment / PR on if you'd like to help change things in the future :)
[02:31:26] <agronholm> the thing is, I'm trying to set up continuous integration
[02:32:42] <agronholm> I have to point pip to a specific filename
[02:32:59] <agronholm> if I use -f, pip will take a long time looking for the packages in PyPI
[02:33:13] <Ivo> --no-index?
[02:33:14] <agronholm> --no-index is a no go because then it can't download deps from pypi
[02:33:24] <Ivo> make a wheelhouse
[02:33:40] <agronholm> a devpi server or something else?
[02:34:11] <Ivo> a wheelhouse can just be a folder
[02:34:23] <Ivo> on filesystem or in a http directory
[02:34:47] <Ivo> build necessary wheels for it with pip wheel -r requirements.txt
[02:34:59] <Ivo> or pip wheel <packages>
[02:35:11] <agronholm> can it read the requirements from my setup.py?
[02:35:20] <agronholm> I don't have a requirements.txt
[02:35:40] <Ivo> then I thnk pip wheel . would work
[02:35:44] <agronholm> ok
[02:35:48] <agronholm> let's see...
[02:35:55] <Ivo> it would build a wheel of your package, and also wheels of the packages it depends on
[02:36:16] <agronholm> I don't want that
[02:36:30] <agronholm> that means there would be plenty of duplication between wheels of my packages
[02:36:57] <agronholm> if I have project A that is depended on by project B
[02:37:01] <agronholm> I build wheels for both
[02:37:15] <agronholm> B's wheel would also contain A and its dependencies
[02:37:20] <agronholm> but B is merely a plugin for A
[02:37:26] <agronholm> you see what I'm getting at?
[02:37:39] <Ivo> eh
[02:37:44] <Ivo> wheels dont contain other wheels
[02:38:08] <Ivo> point the command at the same wheel-dir
[02:41:12] <agronholm> ok, I think I know where to go from here
[02:41:18] <agronholm> thanks for the pointers
[02:41:38] <Ivo> I haven't checked the command looks for duplicates, but I assuem it does
[02:41:48] <Ivo> otherwise you can also use --no-deps for project B
[02:42:10] <agronholm> I'll just put all the wheels in the same dir?
[02:42:36] <Ivo> ja, and then when installing things just use pip install --no-index --find-links=./my/wheelhouse <package>
[02:42:46] <agronholm> yep
[02:43:27] <Ivo> basically what it's designed for, creating a local cache of package wheels
[15:31:48] <Alex_Gaynor> dstufft: is --find-links deprecated (in favor of --extra-index-url)
[15:47:50] <dstufft> Alex_Gaynor: --find-links is not deprecated (because it does something slightly different than --extra-index-url). I want to unify --extra-index-url, --find-links, and --index-url.. I just haven't sorted out how yet
[23:27:09] <kevr> pip3 is trying to use a python 2 setup.py file to install something.
[23:27:28] <kevr> does that mean the package i'm trying to install is only meant for python 2?
[23:45:56] <agronholm> kevr: what are you trying to install?
[23:46:11] <agronholm> and what do you mean by a python 2 setup file
[23:46:20] <agronholm> are there several in the project...?