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
{{ message }}
Repository navigation
Create fully pinned requirements file for bug-fix branches #23548
I spent some time yesterday and today trying to get tests to run on old versions of Matplotlib which....was harder than I wished it would be. We may want to have one very pinned requirements file (possible managed by one of the auto-bump services 😞 or tools) that we rename to fully-pinned-v3.6.x.txt on branching. We can then use that (exclusively) for tests on the backport branch which should hopefully reduce the amount of dep-only backports we have to do (and provide a useful reference for anyone who wants to get old versions testing again).
Hi all - we do not assign issues, so if the issue is open and does not already have an open PR associated with it, it is generally available for contribution. However, please try to coordinate if others have expressed interest in working on the issue recently, so you are not duplicating effort. If you have questions about the best approach for a solution, feel free to post an outline here so we can help.
generate a proposed fully pinned version of our (maybe transient) dependencies
set up one of our jobs on the main branch to use it (maybe?)
on backport make all of the jobs in the bug-fix branch use it
I think this is a good first issue because it requires not special knowledge of Matplotlib, but does require knowledge of packaging and CI (so medium difficulty)
changed the title [-]Create fully pinned requencement file for bug-fix branch [/-][+]Create fully pinned requirements file for bug-fix branches[/+]on Aug 5, 2022
Hi all - we do not assign issues, so if the issue is open and does not already have an open PR associated with it, it is generally available for contribution. However, please try to coordinate if others have expressed interest in working on the issue recently, so you are not duplicating effort. If you have questions about the best approach for a solution, feel free to post an outline here so we can help.
Hi, @tacaswell i would like to contribute on this issue,if you could assign it to me it would be great...
For fixing the bug i think i have to read the docstring first...
Hi all - we do not assign issues, so if the issue is open and does not already have an open PR associated with it, it is generally available for contribution. However, please try to coordinate if others have expressed interest in working on the issue recently, so you are not duplicating effort. If you have questions about the best approach for a solution, feel free to post an outline here so we can help.
Activity
tacaswell commentedon Aug 3, 2022
The work here is
I think this is a good first issue because it requires not special knowledge of Matplotlib, but does require knowledge of packaging and CI (so medium difficulty)
other references: https://zenodo.org/record/6946666 , https://peps.python.org/pep-0665/ , https://github.com/brettcannon/pip-secure-install (maybe we want to use this action?)
[-]Create fully pinned requencement file for bug-fix branch [/-][+]Create fully pinned requirements file for bug-fix branches[/+]navaneethkulal8 commentedon Aug 5, 2023
Interested in working on #23548. Could you please guide me on how to get started with it?
11 remaining items
rcomer commentedon Sep 3, 2025
Yes, I meant the
exclude-neweroptions. I should probably learn to be more verbose!patelishaan commentedon Jan 27, 2026
Hi ! I would like to work on this issue (Create fully pinned requirements file for bug-fix branches #23548) . Please assign it to me
Create fully pinned requirements file for testing (Issue matplotlib#2…
MuhammadArslan012 commentedon Feb 3, 2026
@tacaswell
Hi! Does this issue needs any improvement or it is closed now?
if it needs improvement please assign it to me.
melissawm commentedon Feb 20, 2026
Hi all - we do not assign issues, so if the issue is open and does not already have an open PR associated with it, it is generally available for contribution. However, please try to coordinate if others have expressed interest in working on the issue recently, so you are not duplicating effort. If you have questions about the best approach for a solution, feel free to post an outline here so we can help.
janhaviupadhay1712 commentedon Mar 5, 2026
Hi, I am a new contributor and would like to work on this issue.
Could you please assign it to me?
gy03811-blip commentedon Mar 14, 2026
Hello, I am new to contributing to Matplotlib and exploring beginner issues. I would like to work on this issue if it is still available.
Rahasyapandey commentedon Mar 19, 2026
Hi, @tacaswell i would like to contribute on this issue,if you could assign it to me it would be great...
For fixing the bug i think i have to read the docstring first...
Doc: Clarify set_adjustable behavior for issue matplotlib#23548
kshitiz19deshwal commentedon Mar 26, 2026
Hi, I’d like to work on this issue. Is it still available?
Add pinned requirements file for bug-fix branches
melissawm commentedon Mar 26, 2026
Hi @kshitiz19deshwal , please check the (now) pinned comment:
Add per-release pinned requirements files for bug-fix branch builds
Add per-release pinned requirements files for bug-fix branch builds