-
Notifications
You must be signed in to change notification settings - Fork 515
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
attrdict a requirement for pip install fails otherwise. #2225
Comments
But with python 3.10 on my ArchLinux it is raising the following error:
It seems that |
You need |
My linux unittest started failing due to that too. I sort of expect those kinks to get worked out. And the wheels really should have deployed I think for my OS but I'm not too worried since it bleeding edge. |
@tatarize, what is your OS and Python version? |
@swt2c installing |
Windows 7. Python 3.8 but I also had unittest in linux fail along the same lines it was trying to install wxPython for a thing it didn't really need it for. |
I had the same issue on arch linux recently. If for some reason older versions of wxPython with python 3.10 are needed, you can change the import occurrences of |
It's not only used on Windows, hence why builds are now failing on Linux. At the very least, it is needed when the wheel is built from source (as it always is on Linux). I'm afraid I don't know the inner workings of Here is my pip error log:
|
There isn't any need to narrow it down further. You need to install |
The objection I had was that Linux stopped working. I had some github Linux thing that required wx for unit tests and it threw that error. It didn't work in my windows7 python3.8 setup either since it demanded the attrdict thing. With the merge of not requiring this for Linux this might be closable. I'm used to just getting a valid wheels for windows rather than it trying to compile the whole thing that it doesn't seem like it should have thrown that error at me there either. But, that might be fixable and the Windows10/Python 3.10 system had it install without issue. |
I did just remove wx from the linux unittests since they were never used. So I might not be well versed on all the threads of this issue. |
But the point is that you don't have a choice but to build it on Linux, so if you run |
On Ubuntu 20.04.4 with kernel 5.15 I got almost the same error:
Fixed it with: pip3 install attrdict |
I am getting the same error on CentOS 7.8.2003, python version 3.6.8, wxPython version 4.2.0. Adding attrdict and/or attrdict3 to my requirements file ahead of wxpython does not solve the issue. |
@forchtj I have the same error on wine/windows, python version 3.6.8, wxPython version 4.2.0. But when I downgrade to wxPython 4.1.1, the error was gone. |
Tbh I'm rather disappointed at the devs' lack of response here. This breaks things for Linux users -- for example my CI is now failing for a number of projects and the only sensible fix is to pin |
Which offending commit? |
Thanks for your response! I think this is the one: 2e9169e If I understand correctly, it removes |
No, sorry - that FIXES the problem you're seeing. As a workaround for your CI, you can 'pip install attrdict3' before trying to install wxpython. |
So just to be clear, the intention of What's so important about that commit that it's worth breaking your users for? |
Sorry, but you're misunderstanding the problem. When you're running |
I have the same problem today. I was expecting |
I guess building the 4.2.0 release is broken under modern linuxes because of the attrdict module import. Deleting Line 30 in b567d1e
So those wanting to build 4.2.0 (the latest stable release as of this writing) need to either patch it before building or wait for a new release that rolls in the fix from 2e9169e. |
I'm pretty sure the commit you cited is to fix the issue. What you actually want is the releases of 4.2.0-post1 with that commit in place. Such that installs in Linux are not strange and crashing. We need the pip version to actually work. We don't want to wait a year for that to happen. |
This issue has been mentioned on Discuss wxPython. There might be relevant details there: https://discuss.wxpython.org/t/error-trying-to-pip-install/36381/2 |
It's not possible to install projects that depend on wxPython through pipx due to this bug. |
I've currently got the version of It's been an issue for more than six months now though 😞 |
A fix that worked for me was. Open "Developer Command Prompt for VS 2022" |
Hi, I've installed
|
You need to uninstall
|
You need to uninstall
|
I try all the solution on my testbed and also feed this result to chatgpt, but it also failed. My testbed os is centos 7, python version is 3.9.10. Does anyone solve this issue? |
pip list: attrdict 2.0.1 os-release: CENTOS_MANTISBT_PROJECT="CentOS-7" python version: |
@swt2c Would it be possible to put a point/patch release with the dependency changed to attrdict3 on pip so we don't have to workaround this while waiting for the next version? |
@oyvindln unfortunately, I don't have permissions to create new releases, only @RobinD42 does. Really a more helpful solution would be for Robin to make new wheels for Python 3.11 and 32-bit Windows, which would solve most of these problems. Most people probably do not want to build wxPython from scratch, but just install it. |
Yeah, I actually sort of expected a -Post1 release a while back. I think it's probably fixed but still is causing wxPython to fail kind of universally. I've had to tell more than a couple people to install with ==4.1.1 since it was a bit screwy to get around this thing. |
on my debian 12 system there were the "gtk+ dev" missing sudo apt-get install build-essential libgtk-3-dev some other issues seems to be to have wheel installed before. |
With the release of wxPython 4.2.1, automatic installation is no longer failing. |
It fixed and installed after
pip install attrdict
but I don't usually expect failure to pip install.The text was updated successfully, but these errors were encountered: