Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

gh-121300: Addreplace tocopy.__all__#121302

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Merged
kumaraditya303 merged 6 commits intopython:mainfrommax-muoto:add-replace-to-all
Jul 3, 2024

Conversation

@max-muoto
Copy link
Contributor

@max-muotomax-muoto commentedJul 3, 2024
edited by bedevere-appbot
Loading

Adds missing replace tocopy.__all__

@ghost
Copy link

ghost commentedJul 3, 2024
edited by ghost
Loading

All commit authors signed the Contributor License Agreement.
CLA signed

@bedevere-app
Copy link

Most changes to Pythonrequire a NEWS entry. Add one using theblurb_it web app or theblurb command-line tool.

If this change has little impact on Python users, wait for a maintainer to apply theskip news label instead.

@bedevere-app
Copy link

Most changes to Pythonrequire a NEWS entry. Add one using theblurb_it web app or theblurb command-line tool.

If this change has little impact on Python users, wait for a maintainer to apply theskip news label instead.

Copy link
Member

@serhiy-storchakaserhiy-storchaka left a comment

Choose a reason for hiding this comment

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

LGTM.

error=Error# backward compatibility

__all__= ["Error","copy","deepcopy"]
__all__= ["Error","copy","deepcopy","replace"]
Copy link
Contributor

@pygeekpygeekJul 3, 2024
edited
Loading

Choose a reason for hiding this comment

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

Consider adding a regression test so this doesn't happen again. See helper methodsupport.test__all__ in the test directory—it automatically detects public methods based on whether they follow the public name convention.

Copy link
ContributorAuthor

Choose a reason for hiding this comment

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

Sure, let me go ahead, good callout.

pygeek reacted with thumbs up emoji
@max-muotomax-muotodisabled auto-mergeJuly 3, 2024 05:50
@max-muoto
Copy link
ContributorAuthor

@serhiy-storchaka If you want to take another look.

Copy link
Member

@Eclips4Eclips4 left a comment

Choose a reason for hiding this comment

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

Thanks!

@kumaraditya303kumaraditya303 merged commit7c66906 intopython:mainJul 3, 2024
@miss-islington-app
Copy link

Thanks@max-muoto for the PR, and@kumaraditya303 for merging it 🌮🎉.. I'm working now to backport this PR to: 3.13.
🐍🍒⛏🤖

miss-islington pushed a commit to miss-islington/cpython that referenced this pull requestJul 3, 2024
(cherry picked from commit7c66906)Co-authored-by: Max Muoto <maxmuoto@gmail.com>
@bedevere-app
Copy link

GH-121337 is a backport of this pull request to the3.13 branch.

@bedevere-appbedevere-appbot removed the needs backport to 3.13bugs and security fixes labelJul 3, 2024
JelleZijlstra pushed a commit that referenced this pull requestJul 3, 2024
(cherry picked from commit7c66906)Co-authored-by: Max Muoto <maxmuoto@gmail.com>
@bedevere-bot
Copy link

⚠️⚠️⚠️ Buildbot failure⚠️⚠️⚠️

Hi! The buildbotAMD64 Debian root 3.x has failed when building commit7c66906.

What do you need to do:

  1. Don't panic.
  2. Checkthe buildbot page in the devguide if you don't know what the buildbots are or how they work.
  3. Go to the page of the buildbot that failed (https://buildbot.python.org/all/#builders/345/builds/8418) and take a look at the build logs.
  4. Check if the failure is related to this commit (7c66906) or if it is a false positive.
  5. If the failure is related to this commit, please, reflect that on the issue and make a new Pull Request with a fix.

You can take a look at the buildbot page here:

https://buildbot.python.org/all/#builders/345/builds/8418

Failed tests:

  • test_repl

Failed subtests:

  • test_asyncio_repl_is_ok - test.test_repl.TestInteractiveInterpreter.test_asyncio_repl_is_ok

Summary of the results of the build (if available):

==

Click to see traceback logs
Traceback (most recent call last):  File"/root/buildarea/3.x.angelico-debian-amd64/build/Lib/test/test_repl.py", line199, intest_asyncio_repl_is_ok    assert_python_ok("-m","asyncio")~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^  File"/root/buildarea/3.x.angelico-debian-amd64/build/Lib/test/support/script_helper.py", line182, inassert_python_okreturn _assert_python(True,*args,**env_vars)  File"/root/buildarea/3.x.angelico-debian-amd64/build/Lib/test/support/script_helper.py", line167, in_assert_python    res.fail(cmd_line)~~~~~~~~^^^^^^^^^^  File"/root/buildarea/3.x.angelico-debian-amd64/build/Lib/test/support/script_helper.py", line80, infailraiseAssertionError(f"Process return code is{exitcode}\n"...<10 lines>...f"---")AssertionError:Process return code is -6 (SIGABRT)command line: ['/root/buildarea/3.x.angelico-debian-amd64/build/python', '-X', 'faulthandler', '-I', '-m', 'asyncio']Traceback (most recent call last):xiting asyncio REPL...  File"/root/buildarea/3.x.angelico-debian-amd64/build/Lib/asyncio/__main__.py", line109, inrunraiseOSError(errno.ENOTTY,"tty required","stdin")Fatal Python error: _enter_buffered_busy: could not acquire lock for <_io.BufferedWriter name='<stderr>'> at interpreter shutdown, possibly due to daemon threadsPython runtime state: finalizing (tstate=0x0000562ad21ccb50)Traceback (most recent call last):xiting asyncio REPL...  File"/root/buildarea/3.x.angelico-debian-amd64/build/Lib/asyncio/__main__.py", line109, inrunraiseOSError(errno.ENOTTY,"tty required","stdin")Fatal Python error: _enter_buffered_busy: could not acquire lock for <_io.BufferedWriter name='<stderr>'> at interpreter shutdown, possibly due to daemon threadsPython runtime state: finalizing (tstate=0x000055c24a873b50)

noahbkim pushed a commit to hudson-trading/cpython that referenced this pull requestJul 11, 2024
estyxx pushed a commit to estyxx/cpython that referenced this pull requestJul 17, 2024
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

@JelleZijlstraJelleZijlstraJelleZijlstra approved these changes

@serhiy-storchakaserhiy-storchakaserhiy-storchaka approved these changes

@kumaraditya303kumaraditya303kumaraditya303 approved these changes

@Eclips4Eclips4Eclips4 approved these changes

+1 more reviewer

@pygeekpygeekpygeek left review comments

Reviewers whose approvals may not affect merge requirements

Assignees

No one assigned

Labels

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

7 participants

@max-muoto@bedevere-bot@pygeek@JelleZijlstra@serhiy-storchaka@kumaraditya303@Eclips4

[8]ページ先頭

©2009-2025 Movatter.jp