Skip to content

native: keep same behavior on Python 3.10#1537

Merged
davidism merged 1 commit intopallets:3.0.xfrom
mkrizek:literal_eval-py-310
Nov 9, 2021
Merged

native: keep same behavior on Python 3.10#1537
davidism merged 1 commit intopallets:3.0.xfrom
mkrizek:literal_eval-py-310

Conversation

@mkrizek
Copy link
Copy Markdown
Contributor

@mkrizek mkrizek commented Nov 9, 2021

Checklist:

  • Add tests that demonstrate the correct behavior of the change. Tests should fail without the change.
  • Add or update relevant docs, in the docs folder and in code.
  • Add an entry in CHANGES.rst summarizing the change and linking to the issue.
  • Add .. versionchanged:: entries in any relevant code docs.
  • Run pre-commit hooks and fix any issues.
  • Run pytest and tox, no tests failed.

@davidism davidism added this to the 3.0.3 milestone Nov 9, 2021
@davidism
Copy link
Copy Markdown
Member

davidism commented Nov 9, 2021

Seems appropriate for a bugfix release, can you rebase this to 3.0.x?

@mkrizek mkrizek changed the base branch from main to 3.0.x November 9, 2021 16:30
@mkrizek mkrizek force-pushed the literal_eval-py-310 branch from 2cd8c83 to 0e05fd6 Compare November 9, 2021 16:31
@mkrizek
Copy link
Copy Markdown
Contributor Author

mkrizek commented Nov 9, 2021

Seems appropriate for a bugfix release, can you rebase this to 3.0.x?

Done.

@davidism davidism force-pushed the literal_eval-py-310 branch from 0e05fd6 to bb0db82 Compare November 9, 2021 16:41
@davidism davidism merged commit 99b6fc7 into pallets:3.0.x Nov 9, 2021
@mkrizek mkrizek deleted the literal_eval-py-310 branch November 9, 2021 16:47
@github-actions github-actions Bot locked as resolved and limited conversation to collaborators Nov 24, 2021
@pallets pallets unlocked this conversation May 28, 2025
@davidism
Copy link
Copy Markdown
Member

@mkrizek I'm planning to drop support for Python 3.9, so 3.10 will be the minimum version. I can't remember the context for this fix. Now that 3.10 is the minimum, should we revert this, or continue to avoid literal_eval's leading space behavior?

@mkrizek
Copy link
Copy Markdown
Contributor Author

mkrizek commented May 28, 2025

@davidism I believe reverting this change would break existing templates so we should leave this as is.

@github-actions github-actions Bot locked as resolved and limited conversation to collaborators Jun 12, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants