Skip to content
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

1.3.0 ContextLib Error: ImportError: cannot import name 'nullcontext' #1474

Closed
Leniox opened this issue Jun 30, 2023 · 7 comments
Closed

1.3.0 ContextLib Error: ImportError: cannot import name 'nullcontext' #1474

Leniox opened this issue Jun 30, 2023 · 7 comments

Comments

@Leniox
Copy link

Leniox commented Jun 30, 2023

I believe 1.3.0 is depending on Python 3.7 specific functionality, such as contextlib import nullcontext

contextlib is introduced in Python 3.7

However, the latest conda feedstock for 1.3.0 still relies on python >= 3.6.

Thus, if you use Python 3.6, certain functionalities will fail.

@Leniox
Copy link
Author

Leniox commented Jun 30, 2023

@ogrisel
Copy link
Contributor

ogrisel commented Jun 30, 2023

We don't support Python 3.6 in joblib 1.3.0 anymore:

https://github.com/joblib/joblib/blob/1.3.0/pyproject.toml#L28C16-L28C26

So we indeed need to align the feedstock metadata accordingly to be consistent.

Thanks for the report.

@fcharras
Copy link
Contributor

fcharras commented Jul 3, 2023

To avoid the dependency tree resolution to joblib 1.3.0 for python 3.6 we would also need to yank the joblib 1.3.0 release on conda

@maartenbreddels
Copy link

That would be great, hitting that issue in CI now for vaex.

maartenbreddels added a commit to vaexio/vaex that referenced this issue Jul 7, 2023
@fcharras
Copy link
Contributor

fcharras commented Aug 8, 2023

Was this issue solved after conda-forge/joblib-feedstock#38 ?

@blueivy1117
Copy link

Hi, has this issue been resolved yet? I cannot run DetermineGermlineContigPloidy in my conda environment, returned error with "ImportError: cannot import name 'nullcontext'"

@tomMoral
Copy link
Contributor

tomMoral commented Oct 8, 2023

Yes, the failing release should have been yanked in conda-forge/admin-requests#764

@tomMoral tomMoral closed this as completed Oct 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants