-
Notifications
You must be signed in to change notification settings - Fork 179
set stcal to main, allow python 3.13 #9105
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
I just started regtests on this old PR: #8864 Should I kill that off and start one with this? |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #9105 +/- ##
==========================================
- Coverage 73.73% 73.73% -0.01%
==========================================
Files 373 372 -1
Lines 37276 37285 +9
==========================================
+ Hits 27486 27492 +6
- Misses 9790 9793 +3 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Thanks for checking. I'd say leave them running. I expect failures which would be reason to not rush allowing 3.13. |
|
Would it be overloading the PR to also drop python 3.10 support here? |
I'd say yes. Is there anything preventing dropping python 3.10? The python 3.13 bump requires further regtest investigation right?
Good idea on the upper pin! I'll add that to this PR. |
743910f to
260e63a
Compare
|
The test set run on the closed PR ( https://github.com/spacetelescope/RegressionTests/actions/runs/13037094545 ) were fairly promising - perhaps worth investigating a possible change in numerical behavior for WFSS background subtraction, but the bulk differences look fairly innocuous to me. |
|
A fresh set of regtests with this PR and the python 3.13 regtest branch: https://github.com/spacetelescope/RegressionTests/actions/runs/13077580972 |
|
Regtests show same failures as main |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It looks like there are two additional failing regtests on the first link you sent (PR branch) than on the second link (main), namely test_associations_sdp_pools. What's happening with that?
Also, should we add/update one of the CI jobs to build with 3.13?
|
Thanks!
The 'main' link I shared ran only the fgs tests. Here's the most recent scheduled run on main:
The build job runs cibuildwheel for all supported versions. With this PR this includes 3.13: |
|
The PR causing the failing association tests is now ready for review: #9098 The FGS failures are due to a CRDS delivery prompted by yours truly, which has backfired. Working on a PR now to get those fixed up. |
Thanks, I realized that once I started going through the rest of my notifications this morning.
Thanks, I think this is good enough. I was looking at the environments where the actual unit test suite is run, but I suppose if it runs on 3.12 it'll run on 3.13 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM but we should probably wait for Tyler too
Thanks for the clarification. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One last request, more housekeeping than anything: The quickstart and installation guide documentation both specify python=3.11 during conda environment creation - we should probably either remove the specification, now that we're compatible with the latest release, or at least increment to 3.13.
| You can install the latest development version (not as well tested) from the | ||
| Github main branch: | ||
|
|
||
| | >> conda create -n <env_name> python=3.11 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we need to keep the python specification on all of these, just remove the version pin. Sorry for the imprecise request.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To clarify, do you want this to say python=3.13 or python=3.12? I don't think an unversioned qualifer (python) is supported (but I'm not a conda user so am not sure).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In the past, we did have an unqualified conda create -n <env_name> python, but I'm fine avoiding that to prevent undefined behavior. We can use either, but let's do 3.12 just because it's been thoroughly tested? 🤷
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We've gathered some conflicts during my lack of a response - once this is clean I'll get it merged.
This PR adds support for python 3.13 (and sets the stcal dependency to main as that's the only version that supports 3.13).
Tasks
Build 11.3(use the latest build if not sure)no-changelog-entry-needed)changes/:echo "changed something" > changes/<PR#>.<changetype>.rst(see below for change types)docs/pageokify_regteststo update the truth filesnews fragment change types...
changes/<PR#>.general.rst: infrastructure or miscellaneous changechanges/<PR#>.docs.rstchanges/<PR#>.stpipe.rstchanges/<PR#>.datamodels.rstchanges/<PR#>.scripts.rstchanges/<PR#>.fits_generator.rstchanges/<PR#>.set_telescope_pointing.rstchanges/<PR#>.pipeline.rststage 1
changes/<PR#>.group_scale.rstchanges/<PR#>.dq_init.rstchanges/<PR#>.emicorr.rstchanges/<PR#>.saturation.rstchanges/<PR#>.ipc.rstchanges/<PR#>.firstframe.rstchanges/<PR#>.lastframe.rstchanges/<PR#>.reset.rstchanges/<PR#>.superbias.rstchanges/<PR#>.refpix.rstchanges/<PR#>.linearity.rstchanges/<PR#>.rscd.rstchanges/<PR#>.persistence.rstchanges/<PR#>.dark_current.rstchanges/<PR#>.charge_migration.rstchanges/<PR#>.jump.rstchanges/<PR#>.clean_flicker_noise.rstchanges/<PR#>.ramp_fitting.rstchanges/<PR#>.gain_scale.rststage 2
changes/<PR#>.assign_wcs.rstchanges/<PR#>.badpix_selfcal.rstchanges/<PR#>.msaflagopen.rstchanges/<PR#>.nsclean.rstchanges/<PR#>.imprint.rstchanges/<PR#>.background.rstchanges/<PR#>.extract_2d.rstchanges/<PR#>.master_background.rstchanges/<PR#>.wavecorr.rstchanges/<PR#>.srctype.rstchanges/<PR#>.straylight.rstchanges/<PR#>.wfss_contam.rstchanges/<PR#>.flatfield.rstchanges/<PR#>.fringe.rstchanges/<PR#>.pathloss.rstchanges/<PR#>.barshadow.rstchanges/<PR#>.photom.rstchanges/<PR#>.pixel_replace.rstchanges/<PR#>.resample_spec.rstchanges/<PR#>.residual_fringe.rstchanges/<PR#>.cube_build.rstchanges/<PR#>.extract_1d.rstchanges/<PR#>.resample.rststage 3
changes/<PR#>.assign_mtwcs.rstchanges/<PR#>.mrs_imatch.rstchanges/<PR#>.tweakreg.rstchanges/<PR#>.skymatch.rstchanges/<PR#>.exp_to_source.rstchanges/<PR#>.outlier_detection.rstchanges/<PR#>.tso_photometry.rstchanges/<PR#>.stack_refs.rstchanges/<PR#>.align_refs.rstchanges/<PR#>.klip.rstchanges/<PR#>.spectral_leak.rstchanges/<PR#>.source_catalog.rstchanges/<PR#>.combine_1d.rstchanges/<PR#>.ami.rstother
changes/<PR#>.wfs_combine.rstchanges/<PR#>.white_light.rstchanges/<PR#>.cube_skymatch.rstchanges/<PR#>.engdb_tools.rstchanges/<PR#>.guider_cds.rst