-
-
Notifications
You must be signed in to change notification settings - Fork 18.2k
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
CI: Builds failing in pandas.show_versions()
#44980
Comments
yeah maybe something on a pip release? cc @pandas-dev/pandas-core |
I was looking into this earlier and couldn't reproduce it, even in a clean conda environment with the latest |
looks like 60.0.3 was released to fix this |
60.0.3 did not fix all problems for us unfortunately. When running this locally I get
It looks like it tries to distutils from stdlib, but if running
it is pulling the distutils from
Not sure what is different when doing this via pandas.show_versions() |
This happens because show_version() imports all the dependencies installed including pip and setuptools. Apparently importing pip before setuptools causes this to happen. Swapping these too lines seems to fix it for me. pandas/pandas/util/_print_versions.py Lines 63 to 64 in e18921e
Perhaps its better to wait for an upstream fix, though? |
I couldn't find an upstream bug report about this and I've reproduced it with git HEAD, so I've filed pypa/setuptools#3044. |
Upstream has closed the bug as wontfix. Basically, pip has weird internal expectations that they can't change right now and importing |
Probably fine to just remove |
To workaround this issue one can set an OS environment variable: |
This appears to be correct
gives
as now appearing in pre-release checks https://github.com/simonjayhawkins/pandas-release/runs/6552535479?check_suite_focus=true rerunning the above code sample in a jupyter notebook, gives a warning second time round
switching order of imports, works fine...
|
Failing on all platofrms. E.g.
https://github.com/pandas-dev/pandas/runs/4581277621
The text was updated successfully, but these errors were encountered: