Skip to content

lazy-object-proxy update to 1.5.0 breaks astroid #800

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.

Sign up for GitHub

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

Jump to bottom
Closed
priv-kweihmann opened this issue Jun 10, 2020 · 3 comments · Fixed by #801
Closed

lazy-object-proxy update to 1.5.0 breaks astroid #800

priv-kweihmann opened this issue Jun 10, 2020 · 3 comments · Fixed by #801

Comments

@priv-kweihmann
Copy link
Contributor

Steps to reproduce

  1. locally install lazy-object-proxy==1.5.0
  2. locally install astroid

Current behavior

Exception

Requirement.parse('lazy_object_proxy==1.4.*'), {'astroid'})

Expected behavior

Works as before, as I don't see any breaking changes in lazy-object-proxy
Before e1b4e11 this would have worked
@priv-kweihmann priv-kweihmann changed the title lazy-object-proxy to 1.5.0 breaks astroid lazy-object-proxy update to 1.5.0 breaks astroid Jun 10, 2020
@priv-kweihmann priv-kweihmann mentioned this issue Jun 10, 2020
Merged
2 tasks
algitbot pushed a commit to alpinelinux/aports that referenced this issue Jun 19, 2020
@z3ntu @maxice8
testing/py3-astroid: remove version restrictions
3d96b23 
As done in Arch Linux

See also:
* pylint-dev/astroid@e1b4e11
* pylint-dev/astroid#800
* pylint-dev/astroid#801
@The-Compiler
Copy link
Contributor

pylint/astroid worked just fine for me with lazy-object-proxy==1.5.0 and wrapt==1.12.1 (which I pinned explicitly), so I just noticed this now. What's the point of the pinning in e1b4e11? If it's to avoid backwards incompatibilities, wouldn't just pinning to <2 make more sense?

@priv-kweihmann
Copy link
Contributor Author

priv-kweihmann commented Jun 30, 2020 •
edited
Loading

Maybe it would, I don't know. Better ping the original author?

@Callek
Copy link

Callek commented Oct 21, 2020

@PCManticore can you please elaborate here?

PCManticore pushed a commit that referenced this issue Dec 24, 2020
@priv-kweihmann @PCManticore
Allow lazy-object-proxy >= 1.5.0
744a9a8 
by allowing every version >= 1.4.0

Fixes #800

Signed-off-by: Konrad Weihmann <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Allow lazy-object-proxy >= 1.5.0
3 participants
@The-Compiler @Callek @priv-kweihmann