Skip to content

py-pyqt5: add 5.15.6 and get sources from pypi#29039

Closed
manuelakuhn wants to merge 4 commits intospack:developfrom
manuelakuhn:py-pyqt5-5.15.6
Closed

py-pyqt5: add 5.15.6 and get sources from pypi#29039
manuelakuhn wants to merge 4 commits intospack:developfrom
manuelakuhn:py-pyqt5-5.15.6

Conversation

@manuelakuhn
Copy link
Copy Markdown
Member

General: at the moment py-pyqt5 does not build without #28870 (also before this PR).

The build system has changed to sip-install for newer versions.

Installs with spack install --test=root without problems for all 4 versions.

Side note: The tarballs for versions <=5.13 are not available on the original sources anymore but only via the spack mirror.

@spackbot-app
Copy link
Copy Markdown

spackbot-app bot commented Feb 17, 2022

Hi @manuelakuhn! I noticed that the following package(s) don't yet have maintainers:

  • py-pyqt5

Are you interested in adopting any of these package(s)? If so, simply add the following to the package class:

    maintainers = ['manuelakuhn']

If not, could you contact the developers of this package and see if they are interested? You can quickly see who has worked on a package with spack blame:

$ spack blame py-pyqt5

Thank you for your help! Please don't add maintainers without their consent.

You don't have to be a Spack expert or package developer in order to be a "maintainer," it just gives us a list of users willing to review PRs or debug issues relating to this package. A package can have multiple maintainers; just add a list of GitHub handles of anyone who wants to volunteer.

@spackbot-app spackbot-app bot requested a review from adamjstewart February 17, 2022 14:35
@adamjstewart adamjstewart self-assigned this Feb 17, 2022
@adamjstewart adamjstewart requested a review from Sinan81 February 17, 2022 21:01
@manuelakuhn
Copy link
Copy Markdown
Member Author

@spackbot run pipeline

@spackbot-app
Copy link
Copy Markdown

spackbot-app bot commented Feb 21, 2022

I've started that pipeline for you!

@Sinan81
Copy link
Copy Markdown
Contributor

Sinan81 commented Feb 25, 2022

👀

Comment on lines +71 to +73
with working_dir(self.stage.source_path):
sip = Executable(join_path(spec['py-sip'].prefix.bin, 'sip-install'))
sip(*self.build_args())
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Instead of using sip-install, is it possible to build with pip? Since sip is now a build-backend listed in pyproject.toml it should theoretically work with other Python build tools like pip and build.

Then, once the older versions are removed, we can directly subclass PythonPackage and delete SIPPackage entirely. I think we would have to deprecate py-pyqt4 first too. There's also a new py-pyqt6 package on PyPI.

Conversely, is it possible to build older versions with sip-install? What about py-pyqt4? Just trying to see if we can keep things uniform and/or reduce the number of build systems we support.

@adamjstewart
Copy link
Copy Markdown
Member

Ping @manuelakuhn

@Sinan81
Copy link
Copy Markdown
Contributor

Sinan81 commented Oct 14, 2022

sorry. totally forgot about this. I'll review it soon.

@manuelakuhn
Copy link
Copy Markdown
Member Author

Sorry for the delayed answer. I think there are some issues with this package now (doesn't build anymore) due to the age of this PR. I will have a look.

@adamjstewart adamjstewart mentioned this pull request Nov 22, 2022
6 tasks
@adamjstewart
Copy link
Copy Markdown
Member

I'm working on this in #32696

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants