Log file Viewer

[05:23:38] <nyrk> nanonyme: I inverted egg and wheel again, egg where the most recent in my mind, but according to https://packaging.python.org/wheel_egg/ it's wheel right :)

[05:23:58] <nyrk> so question was for wheel yes

[05:26:14] <nyrk> exif support for python on windows is very poor, pure python packages are very limited, there's no exiftool wrapper for write (as far as I could see), there is py3exiv2 I cannot compile for the error I mentionned and I wasn't able to compile exifyay either

[05:26:52] <nyrk> I had to fallback on generating a CSV and then let exiftool do the job from the csv ..

[06:27:35] <hyperair> hi, i'm trying to figure out if this is a bug: https://gist.github.com/hyperair/8538cfc4962311a93dc258f29cfe661a. basically when installing a requirements.txt that force a conflict, the first installation works, but the second installation using the same requirements file doesn't if the .egg-info directory is removed.

[14:47:07] <dw> just reiterating my question from 2 days back.. anyone familiar with a better approach to distributing binary wheels for multiple statically-linked library variants, other than just a separate package upload to pypi? thinking <pkgname>_master with a slightly hacked setup.py to support that

[14:47:17] <dw> setuptools extras doesn't seem to cover this sanely

[14:51:51] <Siecje> Can you create a wheel for a extras_require package?

[16:47:49] <agronholm> Siecje: what does that mean? pretty sure they're packages like the rest?

[16:59:12] <Siecje1> agronholm: Because he was asking how to create a wheel for a branch without creating a new pypi package. Wouldn't that work for it?

[16:59:40] <agronholm> a branch, like in a VCS branch?

[16:59:45] <agronholm> checkout, build wheel, done?

[17:05:38] <Siecje1> That would require everyone to build the wheel.

[17:06:42] <agronholm> for what?

[17:07:03] <agronholm> does this person want to publish wheels for a different project?

[17:07:12] <agronholm> or maybe under a different version?

[17:07:26] <Siecje1> dw: wants to publish wheels for a branch. I assume.

[17:07:43] <ngoldbaum> each branch would need a setup.py file that defines a unique package name

[17:07:45] <agronholm> previously you said extras_require

[17:07:51] <agronholm> now it's branches?

[17:08:09] <Siecje1> agronholm: I thought maybe you could use extras_require to do it. So you install package[branch]

[17:08:17] <agronholm> no

[17:08:23] <Siecje1> okay sorry

[17:08:23] <agronholm> extras_require is for something very different

[17:08:38] <ngoldbaum> extras_require lets you install additional packages from pypi that are needed for optional functionality

[17:08:54] <ngoldbaum> and define which additional packages are needed for each piece of additional functionality

[18:31:25] <dw> Siecje: i tried tricking pip into it, but i couldnt' figure out how (extras_require package)

[18:32:01] <dw> i can do it with a single setup.py that looks for an env var and changes package name based off it, or if env var is unset, hidden file in the distribution that accomplishes same effect

[18:33:54] <dw> Siecje: and by 'tricking pip into it', i mean, i mocked up a demo setup.py and ran pip install .[extra] then hoked through its cache directory, but the filenames in the cache suggest it paid no attention to the extras specification