-
-
Notifications
You must be signed in to change notification settings - Fork 35
Can't install lazy-object-proxy via Pip on macOS #70
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I need to figure out how this was build. Any details on what build env you had? This must have been built from source and you see that bad build ended up in your cache. |
This happens on all macOS versions I tried, including Ventura, and also with the new pip 22.3.
This doesn't seem to be related to caching, as it also happens with the cache disabled:
Version 1.8.0 doesn't work either. |
Does |
In my "sandbox" with pip 22.2.2 and python 3.10, when using
|
|
Or it may be a setuptools thing (in the past it used to do that local install of deps in that |
This may be it: https://setuptools.pypa.io/en/stable/history.html#v52-0-0 Regarding the original report from @phst - I cannot reproduce this. I wonder if this is some sort of osx specific issue.... @RonnyPfannschmidt pls help :-) |
Nothing comes to mind, i currently don't have the bandwidth to debug this It's likely old versions |
No worries. @phst I think we need more info about your machine ( |
|
|
I've now upgraded all outdated packages, which succeeded except for |
Have you tried implementing my original suggestion?
|
@phst I found a fix that helped, for me at least. I had to install setuptools-scm using pip. Apparently that was a dependency for lazy-object-proxy that I did not have. Once I ran pip install lazy-object-proxy after getting setuptools-scm, it worked like a charm. |
Released 1.9.0 with some bump in min versions for setuptools-scm. Lemme know if this still reproduces. |
Doing a clean install on a new mac, had the same issue with 1.9.0. Manual install of setuptools-scm fixed the issue. |
I still believe it's homebrew customizing the python installation the wrong way. You should take it in their bugtracker if you care. I don't have a mac so you can guess how much :-) |
Installing 1.9.0 appears to work fine for me, thanks! |
This reverts commit 514d2aa. Newer versions of Pylint don't depend on lazy-object-proxy any more, so this workaround should no longer be required.
This reverts commit 514d2aa. Newer versions of Pylint don't depend on lazy-object-proxy any more, so this workaround should no longer be required.
The last version that works for me is 1.4.1, and I think the problem is that 1.4.2 introduced a pyproject.toml file that doesn't specify a version number. So maybe the fix is to include a version number in pyproject.toml (and add a corresponding entry to .bumpversion.cfg).
The text was updated successfully, but these errors were encountered: