You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
i'm guessing you are getting the sdist rather than the wheel. if i'm correct then it would be good to identify why that is happening. if i'm wrong, then perhaps you could provide more context about your setup and how you are installing things etc.
Yes. (context: developing an addon for FreeCAD, which uses pyside6 for the UI, but I dont need any of the pyside component for development, just the types so I know how to access the API.)
P.S.: Actually, it would be nice if the stubs could include the doc-strings. But that is a minor request.
ok, i got it now. you'll want to have pip install it without installing deps. python -m pip install --no-deps pyside6-stubs for example. yes this is annoying for your case. yes there can be options in various install cases to call this out in a config file.
there's always a question here on these sorts of auxiliary packages. how should they express what version(s) of the main package they work with? last i worked on this group of stubs, python had no way to express that outside of a dependency. in some cases i used an extras dependency group so that people could opt in to the expression of that constraint when they wanted to. this package happens not to.
just as general context, these qt stubs packages haven't been particularly active for awhile. just around expectations of things changing etc. but, happy to keep chatting about solving your scenario.
Yes, I figured out the no-deps option after I installed the stubs twice. The reason why I ask is because I want to define the stubs as (optional) development dependencies in my project. Now the toml doesnt allow you to declare no-deps on a dependency, so I cannot tell users to install dev-dependencies because that will automatically download the 1.4gb pyside6 package. I find it odd that when you try to intall stubs, the stubs will install the whole package too. That is just counter-intuitive. In my opinion, the pyside6 package should be an optional dependency for these stubs.
After thinking about this, I think the dependency on pyside6 can be dropped.
The case where the user needs to install Pyside6-stubs and wanted also PySide6 but did not figure to put it in his requirements looks very unlikely to me. People are using the stubs after they have installed the GUI.
i'm applying this pattern of an optional extra that can be used to enforce compatibility constraints we may want to express across all four stubs repos.
of course... ci is broken. :] so working through fixing that up. i don't know the release process offhand so i'm not promising i get everything done, but i'm trying to get the code changes in anyways.
well, this is embarassing... this isn't the pyqt6-stubs on pypi. so hey, you got me to make some improvements here, but you might be looking for https://github.com/blackteahamburger/PyQt6-stubs? they got the pypi name. i didn't realize that... sheesh. it does appear to be derivative (no complaint) but does not share git history. guess you'll have to go talk through it with them now. sorry. :[
Activity
altendky commentedon Oct 22, 2026
i'm guessing you are getting the sdist rather than the wheel. if i'm correct then it would be good to identify why that is happening. if i'm wrong, then perhaps you could provide more context about your setup and how you are installing things etc.
relikd commentedon Oct 22, 2026
Just
pip install pyside6-stubsin a venv (macOS). Same happens withuvaltendky commentedon Oct 22, 2026
thanks. are you intending to use this package installed without pyside6?
relikd commentedon Oct 22, 2026
Yes. (context: developing an addon for FreeCAD, which uses pyside6 for the UI, but I dont need any of the pyside component for development, just the types so I know how to access the API.)
P.S.: Actually, it would be nice if the stubs could include the doc-strings. But that is a minor request.
altendky commentedon Oct 22, 2026
ok, i got it now. you'll want to have pip install it without installing deps.
python -m pip install --no-deps pyside6-stubsfor example. yes this is annoying for your case. yes there can be options in various install cases to call this out in a config file.there's always a question here on these sorts of auxiliary packages. how should they express what version(s) of the main package they work with? last i worked on this group of stubs, python had no way to express that outside of a dependency. in some cases i used an extras dependency group so that people could opt in to the expression of that constraint when they wanted to. this package happens not to.
just as general context, these qt stubs packages haven't been particularly active for awhile. just around expectations of things changing etc. but, happy to keep chatting about solving your scenario.
relikd commentedon Oct 22, 2026
Yes, I figured out the no-deps option after I installed the stubs twice. The reason why I ask is because I want to define the stubs as (optional) development dependencies in my project. Now the toml doesnt allow you to declare no-deps on a dependency, so I cannot tell users to install dev-dependencies because that will automatically download the 1.4gb pyside6 package. I find it odd that when you try to intall stubs, the stubs will install the whole package too. That is just counter-intuitive. In my opinion, the pyside6 package should be an optional dependency for these stubs.
altendky commentedon Oct 22, 2026
i described two approaches that have been taken here, and yes, an extras (optional) dependency is one of them.
let's see if @bluebird75 cares to chime in even just with an opinion here. they did all the work on this project.
bluebird75 commentedon Oct 23, 2026
After thinking about this, I think the dependency on pyside6 can be dropped.
The case where the user needs to install Pyside6-stubs and wanted also PySide6 but did not figure to put it in his requirements looks very unlikely to me. People are using the stubs after they have installed the GUI.
altendky commentedon Oct 23, 2026
i'm applying this pattern of an optional extra that can be used to enforce compatibility constraints we may want to express across all four stubs repos.
of course... ci is broken.
:]so working through fixing that up. i don't know the release process offhand so i'm not promising i get everything done, but i'm trying to get the code changes in anyways.altendky commentedon Oct 23, 2026
well, this is embarassing... this isn't the pyqt6-stubs on pypi. so hey, you got me to make some improvements here, but you might be looking for https://github.com/blackteahamburger/PyQt6-stubs? they got the pypi name. i didn't realize that... sheesh. it does appear to be derivative (no complaint) but does not share git history. guess you'll have to go talk through it with them now. sorry.
:[altendky commentedon Oct 23, 2026
wait no, that's pyqt6... bother. too many tasks today.
altendky commentedon Oct 23, 2026
@bluebird75, you interested in either doing a release or adding me on the pypi projects in case i get around to it?
bluebird75 commentedon Oct 24, 2026
@altendky sure, I'll add you with pleasure
Note that Qt is now actively fixing reported typing issues. So this repository is going to be obsoleted one day or the other
altendky commentedon Oct 24, 2026
Thanks! Also, these projects being pointless would be awesome... So glad to hear there is progress from qt.