docs update

[niketh-keshavan]

No description provided.

[altendky]

let me know when this is ready and i'll merge. i just figured out the read the docs integration issue i think so should be able to release when you're ready. and yeah, you'll find more and we'll release again. i just need to have the process working. it's been awhile...

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 99.90%. Comparing base (6a83985) to head (07cf634).

Additional details and impacted files

@@               Coverage Diff               @@
##           release/v0.8.0     #295   +/-   ##
===============================================
  Coverage           99.90%   99.90%           
===============================================
  Files                  35       35           
  Lines                2101     2101           
  Branches              294      294           
===============================================
  Hits                 2099     2099           
  Misses                  1        1           
  Partials                1        1           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[niketh-keshavan]

LGTM. Issues will come up (how it goes...) but those can be addresses as they appear rather than holding indefinitely.

[altendky]

yeah, part of releasing quick here is just to find and work out the bugs in that process... so next time is easier again.

[altendky]

i'm not necessarily against it, but what is the reason for dropping pyside2 at this point? having at least one version that works on both can be nice for any of the (very few i suspect) other folks that might be using this.

[niketh-keshavan]

i'm not necessarily against it, but what is the reason for dropping pyside2 at this point? having at least one version that works on both can be nice for any of the (very few i suspect) other folks that might be using this.

I thought (incorrectly) that PySide 2 supported only up to 3.9. I'll update this, don't see any reason to keep it out

[altendky]

ah yeah, all those ragged matrix conditions... a pain. :[ thanks, i'll keep an eye out here.

[niketh-keshavan]

ah yeah, all those ragged matrix conditions... a pain. :[ thanks, i'll keep an eye out here.

I'll follow your suggestions here. I'm not against developing a workaround for 5.15.2.1, but at the same time deprecating (or even just leaving it claimed untested) may be easier.

[altendky]

i'll take a look in the morning, thanks

[altendky]

ok, i missed the morning. and actually i'm starting with a question i guess. was there a failure you were seeing that lead to removing it? or do we just need to remove the removal notices from this pr

[niketh-keshavan]

I guess I'm a bit confused here, I though 5.15.2.1 was the only Pyside 2 version compatible with 3.10 and currently:

pyside2 ~= 5.15, != 5.15.2, != 5.15.2.1

[niketh-keshavan]

Also, the matrix currently excludes Pyside 2. I didn't see any errors, but it's also not getting tested.

Ha, for fun I reenabled 5.15.2.1 on my fork and it passed all CI. Let me open a PR (or update this one) here and see if it does the same.

[niketh-keshavan]

So, pytest-qt doesn't have support for Pyside 2 past 4.4.0. To maintain Pyside 2 testing this version could be forced, or Pyside 2 could just be left in untested. It's not like I was seeing specific errors before to remove it, it was just fully excluded from tests.

[altendky]

thanks. i think its fine to leave it untested for now. i do tend to keep support around too long (pytest-twisted still runs on py2...) and it would be good to consider removal. we are indeed down to a very small potential support area there.

[niketh-keshavan]

Seems ready to merge to me (minus whatever this codecov issue is). If it's worth looking into, let me know and I'll get it done before release.

Codecov failing from MacOS runners busy. Should pass once they run.