ChatCrawlersearch across public Telegram Open the app
Q

Qt for Python (PySide/Shiboken)

4 May 2022
2022-05-04×
4 May 2022
K
Ссылка
click to show
Can anyone help me shed some light on why I can't build PySide 6.3.0?: https://gist.github.com/keithel/2b18e36471b46225ff005ceb84e6abaf ImportError: cannot import name 'build_py' from 'setuptools._distutils.command' (/home/vagrant/Build/swift-nav/console_pp/py39/lib/python3.9/site-packages/setuptools/_distutils/command/__init__.py) setuptools/_distutils/command/build_py.py exists, and does define a class called build_py...
K
Cristián 🥑maybe updating setuptools?
Well, that took longer than I thought to test.. My build script kept wiping out the python env and recreating it, so my setuptools upgrade was just being thrown away. Now that I fixed the script, and setuptools is up-to-date (62.1.0), it still fails in the same manner.. I don't understand what it's complaining about.
C
no idea, but clearly the issue is between distutils and setuptools. So the thing is that locally we migrated from distutils to setuptools. In later version setuptools included some distutils functionallity to enable a better migration. You might want to do the from setuptools.command.build_py import build_py as _build_py command on a shell instead of running the whole build script and try to find the proper version that is working for you. Setuptools is a big module that's changing quite a lot, you might need a lower version as well, but I cannot tell you from the top of my heart which one. Some of them had issues, and we blacklisted some of them before 48.0, but maybe some around 5X.YY or installing manually distutils might help, but again, be aware of versions. Couldn't find any open issue, so it might be a problem with the latest.
K
I'm going to try some older setuptools versions.
C
mmm but on the error setuptools is on 60.5.0 (gistfile1.txt) and on the repl 62.1.0) I hope you tried to reproduce the error on the repl with the 60.5 version
C
if the repl doesn't fail, then something's messing up with the build instruction directly
K
One suggestion I got was it could be an interaction with setuptools-rust
aah wait a sec...are you using a virtual environment? I mean if you activate it then it's just 'python', no need to specify the whole path. If you are using pyenv, then I must confess I know like 3 errors that I never managed to solve from using the python versions directly
C
well, any rust interaction is a completely new area, so then you will be on your own :S
I'm not using a virtualenv - I'm using a standalone py install that gets destroyed and rebuilt with each build invocation (through cargo).
I tried using a virtualenv with this particular python, but some paths built into the python install made it not possible to build PySide through a virtualenv created from that python.
I have a patch that I think works around that
Cristián 🥑well, any rust interaction is a completely new area, so then you will be on your own :S
Rust is out of the picture now. I was able to reproduce the same error with a virtualenv created from default Python 3.8.10, default setuptools installed with it (44.0.0). The python env is what you get with a fresh Ubuntu 20.04 installation, with just the packages listed installed (setuptools, wheel, packaging) (not including the packages that the distro pre-installs with the python install). https://gist.github.com/keithel/2b18e36471b46225ff005ceb84e6abaf#file-also-fails-from-a-venv-created-from-default-installed-ubuntu-20-04-python-3-8
K
The common thing amongst all these tests is that I'm trying to build from the 6.3 branch of pyside-setup... I should try dev.
Calendar: May 2022
Archive by month
Open in Telegram Каталог площадок Искать в ChatCrawler

A snapshot of an open public feed from the search index ChatCrawler — “Google for public Telegram”; refreshed as the venue is crawled. Times are UTC.

Public content only, official Telegram API. About · FAQ · What we do not do · Remove a page · Catalog