Subprocess error, looking for attrdict module but not finding it about pipgrip

[Porkepix]

@ddelange I understand the source of the issue and mentioned it in the issue you can see above, but publishing Linux wheels doesn't seems to be something planned for now. I understand it's kind of an issue to manage such cases and that #40 you pointed out tries to solve the issue. While it's not yet the case, maybe is it at least possible to have a clean error message (that might even point out to that issue!) rather than a harsh exception (not even visible when ran by Homebrew btw)?

EDIT: And thanks for the explanation, of course!

[ddelange]

Hi @Porkepix 👋

Will close this issue as duplicate of #40 (see #52 for another example of failing source build).

This is a downstream issue with wxPython not (yet) publishing wheels for your current environment (mix of cpu architecture, os, python version and implementation. See also first line of your command output above. You can confirm the issue by searching on pypi.org and inspecting the wheel filenames under downloads. In this case ( is probably a trivial fix in their source installation instruction set for linux.

To avoid source install (tar.gz), there are beautiful CI setups out there to get wheels uploaded for pretty much the whole matrix. Here's a package that can work with limited ABI, so there they can build py36 wheels that are upward compatible, and so a linux x86 py36 abi3 wheel will smoothly install in your particular py310 env. For example giampaolo/psutil#2103. Adopting such a solution, however, is up to the upstream maintainers & contributors.

Hope that helps!

[ddelange]

not even visible when ran by Homebrew btw

definitely looking into that!

agreed that the error message could be more verbose and link to #40

[ChrisBarker-NOAA]

Just coming from the side here, but it certainly SHOULD be possible to determine dependencies without using platform specific wheels.

Maybe this is a still a gap in the toolchain(s) though -- if a package is built from old-style setup.py :-(

[ddelange]

Yes, it's a classic I'm afraid ref pypa/pip#1884

for instance, if there's no Mac wheel, it might be that the project does something like install_requires=['torchvision==0.10.0;sys_platform=="darwin"'], and so you will need to run through all of setup.py to find out the correct dependencies, as the linux wheel won't contain this dependency.

[ChrisBarker-NOAA]

Och! that's even worse than I thought.

It seems it wouldn't have been too hard to add a requirements specification to the sdist spec years ago, but ohh well.

-CHB

[ddelange]

Yes, py ecosystem can be a bit of a headache at times. Too many wasted hours was the trigger for me to publish this package in the first place... Ran into more walls in #45