Skip to content

Fix Python 3.11 issue for pprint_include/exclude_names - #13639

Merged
pllim merged 2 commits into
astropy:mainfrom
taldcroft:table-py3.11-compat
Sep 12, 2022
Merged

pllim merged 2 commits into
astropy:mainfrom
taldcroft:table-py3.11-compat

Conversation

@taldcroft

@taldcroft taldcroft commented Sep 12, 2022 •

Copy link
Copy Markdown
Member

Description

This pull request is to the Python 3.11 failure in test_pprint which is due to a change in behavior for OrderedDict.pop() (presumably python/cpython#27530).

This PR restores the Python <= 3.10 behavior where removing a column ends up calling TableColumns.__delitem__.

I ran the astropy unit tests with Python 3.11-rc1 and the table tests passed. BTW, the Table tests took 21.8 sec with Python 3.8 and 8.3 sec with Python 3.11. Wow! I want.

Fixes #13637

Checklist for package maintainer(s)

This checklist is meant to remind the package maintainer(s) who will review this pull request of some common things to look for. This list is not exhaustive.

  • Do the proposed changes actually accomplish desired goals?
  • Do the proposed changes follow the Astropy coding guidelines?
  • Do the proposed changes need the code-style fixed?
  • Are tests added/updated as required? If so, do they follow the Astropy testing guidelines?
  • Are docs added/updated as required? If so, do they follow the Astropy documentation guidelines?
  • Is rebase and/or squash necessary? If so, please provide the author with appropriate instructions. Also see "When to rebase and squash commits".
  • Did the CI pass? If no, are the failures related? If you need to run daily and weekly cron jobs as part of the PR, please apply the Extra CI label.
  • Is a change log needed? If yes, did the change log check pass? If no, add the no-changelog-entry-needed label. If this is a manual backport, use the skip-changelog-checks label unless special changelog handling is necessary.
  • Is this a big PR that makes a "What's new?" entry worthwhile and if so, is (1) a "what's new" entry included in this PR and (2) the "whatsnew-needed" label applied?
  • Is a milestone set? Milestone must be set but astropy-bot check might be missing; do not let the green checkmark fool you.
  • At the time of adding the milestone, if the milestone set requires a backport to release branch(es), apply the appropriate backport-X.Y.x label(s) before merge.

@taldcroft

Copy link
Copy Markdown
Member Author

pre-commit.ci autofix

@taldcroft taldcroft mentioned this pull request Sep 12, 2022
10 tasks done
@taldcroft
taldcroft requested a review from mhvk September 12, 2022 09:21
@Cadair

Cadair commented Sep 12, 2022

Copy link
Copy Markdown
Member

I have merged this into #13614 to let it run in the CI as well fwiw.

@pllim pllim left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Seems to fix the Python 3.11 errors over at Stuart's PR, so I am approving. Thanks!

@mhvk

mhvk commented Sep 12, 2022

Copy link
Copy Markdown
Contributor

Belated approval... Makes sense to just try to fix the problem keeping the behaviour identical for now.

pllim added a commit that referenced this pull request Sep 12, 2022
…639-on-v5.0.x

Backport PR #13639 on branch v5.0.x (Fix Python 3.11 issue for pprint_include/exclude_names)
pllim added a commit that referenced this pull request Sep 12, 2022
…639-on-v5.1.x

Backport PR #13639 on branch v5.1.x (Fix Python 3.11 issue for pprint_include/exclude_names)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Decide how to handle Python 3.11 table test failure

4 participants