Error during wx installation via pip on linux

[DarkFenX]

See #1861 for details

[DarkFenX]

@ForlornWongraven, i tried installing dependencies on my debian rig in venv, and it worked perfectly: https://gist.github.com/DarkFenX/c20b7ac2f9b1676abf6112ceea2f9fa2

Could you provide following info:

• full pip installation log (pip3 install -v --no-cache-dir --log pyfa_reqs.log -r requirements.txt, remove nocache if it's causing issues)
• do you have pyyaml for python3 installed as system package? If yes, which version is it?

[ForlornWongraven]

Sorry for the late reply. I purged my system of a few applications and dnf removed some python3 packages. Now that I had time to check again I also found that pathlib2 was needed to compile wxPython.

pyyaml is not installed as system package.

log.txt

[DarkFenX]

I do not see any errors in the log. In fact, it does not have any traces of installation of anything - i suppose because you did not install dependencies on a clean system / clean venv.

[ForlornWongraven]

I misunderstood your request, sorry. I did set up a new env just to test this again. Here is the log.

I highlight this:

   "/home/forlorn/test/bin/python3" -u build.py build
   Traceback (most recent call last):
      File "build.py", line 30, in <module>
        import pathlib2
    ModuleNotFoundError: No module named 'pathlib2'
    Command '"/home/forlorn/test/bin/python3" -u build.py build' failed with exit code 1.

pyfa_reqs.log

[DarkFenX]

This is upstream issue wxWidgets/Phoenix#1251. I am unsure if we can do anything about it. Even if I would have added it as entry into requirements.txt as workaround - pip still won't follow order specified in the file and it may pick wxpython before installing pathlib2.

[Bazzek]

maybe making 2 requirements files (requirements_1st.txt and requirements_main.txt) could be an option?

[DarkFenX]

Maybe. But bear in mind that this is linux-specific bug (because only on linux you need to build wx when installing via pip, on other platforms it's provided as precompiled binary). So doing extra file and extra instructions sounds like excessive for me, given:

a) it's an upstream bug
b) which has rather clear error output
c) for specific platform (linux)
d) for this specific platform you have to install c/c++ development files via trial and error (maybe you had them installed on your PC, but on default linux installations I am confident that bunch of them is missing, I had to install a few on my Debian while verifying this bug)

[Bazzek]

Fair enough, was nothing more then a noob trying to think along with the problem. You make a solid point though

[rnrsr]

just as an FYI, if you run pip3 install pathlib2 it resolves this.

[Asday]

The linked wxPython issue seems to think this is fixed, but pip install -r requirements.txt after virtualenv --python=$(which python3.6) env and . env/bin/activate still fails for the same reason.

I was of course able to get past it by manually installing pathlib2, but I would love to see this revisited.

[DarkFenX]

we're still using 4.0.6. 4.0.7 had several issues with it (which were fixed by 2 or 3 post-releases) and i was waiting until more issues appear, and then just forgot to update.

[DarkFenX]

I bumped versions of some dependencies, wx included. Please try if it causes any issues on latest master.

[Asday]

Works perfectly.

[DarkFenX]

Cool, closing