GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — [3.11] gh-100546: Remove incorrect positional-only marker from eval (GH-100547) by miss-islington · Pull Request #100654 · python/cpython

Conversation

@miss-islington

@miss-islington miss-islington commented Jan 1, 2023 •
edited by bedevere-bot
Loading

Uh oh!

There was an error while loading. Please reload this page.

Copy link
Copy Markdown
Contributor

All the arguments are positional-only.

The current status after GH-99476 seems to be to not use positional-only
markers in documentation, hence I've simply removed it.
(cherry picked from commit 71159a8)

Co-authored-by: Shantanu [email protected]

  • Issue: eval() documentation is wrong about keyword arguments #100546

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.
All reactions
@hauntsaninja @miss-islington
pythongh-100546: Remove incorrect positional-only marker from eval (p…
13173f8 
…ythonGH-100547)

All the arguments are positional-only.

The current status after pythonGH-99476 seems to be to not use positional-only
markers in documentation, hence I've simply removed it.
(cherry picked from commit 71159a8)

Co-authored-by: Shantanu <[email protected]>
This was referenced Jan 1, 2023
eval() documentation is wrong about keyword arguments #100546
Closed
gh-100546: Remove incorrect positional-only marker from eval #100547
Merged
@bedevere-bot bedevere-bot added skip news awaiting review docs Documentation in the Doc dir labels Jan 1, 2023
hauntsaninja
hauntsaninja approved these changes Jan 1, 2023
View reviewed changes
@bedevere-bot bedevere-bot added awaiting merge and removed awaiting review labels Jan 1, 2023
@miss-islington
miss-islington merged commit 7ed7127 into python:3.11 Jan 1, 2023
@bedevere-bot bedevere-bot removed the awaiting merge label Jan 1, 2023
@miss-islington
miss-islington deleted the backport-71159a8-3.11 branch January 1, 2023 01:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@hauntsaninja hauntsaninja hauntsaninja approved these changes

Uh oh!

There was an error while loading. Please reload this page.

Assignees

No one assigned

Labels

docs Documentation in the Doc dir skip news

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Uh oh!

There was an error while loading. Please reload this page.

3 participants

@miss-islington @hauntsaninja @bedevere-bot
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
You are visitor 01402503 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.