Skip to content

Rename constraints param of DefaultIsolatedEnv.install - #1160

Merged
layday merged 1 commit into
pypa:mainfrom
layday:layday/rename-env-install-constraints-param
Aug 28, 2026
Merged

Rename constraints param of DefaultIsolatedEnv.install#1160
layday merged 1 commit into
pypa:mainfrom
layday:layday/rename-env-install-constraints-param

Conversation

@layday

@layday layday commented Aug 16, 2026

Copy link
Copy Markdown
Member

Description

This is a vestige from a previous version where the constraints.txt file was incorrectly interpreted as a requirement list.

Changelog

  • Added changelog fragment: docs/changelog/<pr_number>.<type>.rst
    • Types: feature, bugfix, doc, removal, misc
    • Example: 123.feature.rst containing Add custom backend support - by :user:`yourname`

Checklist

  • Tests pass locally (tox)
  • Code follows project style (tox -e fix)
  • Type checks pass (tox -e type)
  • Documentation builds (tox -e docs)

@layday
layday force-pushed the layday/rename-env-install-constraints-param branch 2 times, most recently from 5e07883 to 5e6fcb6 Compare August 16, 2026 09:34
@layday layday added this to the v2.0.0 milestone Aug 16, 2026
@layday
layday force-pushed the layday/rename-env-install-constraints-param branch 3 times, most recently from 813f8df to ca2a4cc Compare August 17, 2026 17:54

@gaborbernat gaborbernat left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Wouldn't this be a breaking change?

@layday

layday commented Aug 17, 2026

Copy link
Copy Markdown
Member Author

Technically, yes. It’s why I’ve put it under the v2 milestone. I’m hoping to revamp the util module for a new major release; this can go in with it.

@henryiii

Copy link
Copy Markdown
Contributor

I checked pyodide-build, it doesn't use this arg.

@layday
layday force-pushed the layday/rename-env-install-constraints-param branch from ca2a4cc to 115404a Compare August 18, 2026 10:05
@gaborbernat

Copy link
Copy Markdown
Contributor

I'm not sure if we need this, but if you strongly feel about this, we should take this moment to add it to the entire library and collect similar breaking changes so we can do one pass through it.

That being said, I want to hold on to this change until we cut a new release for version one of all the non-breaking changes we already have on the main and it's not released.

@layday

layday commented Aug 18, 2026

Copy link
Copy Markdown
Member Author

I agree, that's why I've been filing some of these changes under v2. See above:

Technically, yes. It’s why I’ve put it under the v2 milestone. I’m hoping to revamp the util module for a new major release; this can go in with it.

@gaborbernat

Copy link
Copy Markdown
Contributor

Can we keep this pull request draft until we cut the release of the latest main branch under version 1, then?

@layday

layday commented Aug 18, 2026

Copy link
Copy Markdown
Member Author

Sure.

@layday
layday marked this pull request as draft August 18, 2026 11:54
@layday
layday force-pushed the layday/rename-env-install-constraints-param branch from 115404a to e73b707 Compare August 18, 2026 18:32
@layday
layday force-pushed the layday/rename-env-install-constraints-param branch from e73b707 to e868db8 Compare August 28, 2026 10:23
@layday
layday marked this pull request as ready for review August 28, 2026 10:24
@layday
layday force-pushed the layday/rename-env-install-constraints-param branch 2 times, most recently from f83252b to 93143bb Compare August 28, 2026 10:28
This is a vestige from a previous version where the constraints.txt
file was incorrectly interpreted as a requirement list.
@layday
layday force-pushed the layday/rename-env-install-constraints-param branch from 93143bb to 8318ce9 Compare August 28, 2026 20:49
@layday
layday enabled auto-merge (squash) August 28, 2026 20:49
@layday
layday merged commit 8ec7ae2 into pypa:main Aug 28, 2026
111 of 113 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants