| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
No; this PR represents an atomic change. Documentation (and preferably tests) follow. Your previous PR consisted of two different changes1. But you cannot just remove the existing API; you need to keep it and deprecate it (see PEP-387). Footnotes
|
Sorry, something went wrong.
|
Here's an example of deprecation: #105397 |
Sorry, something went wrong.
|
The question may seem silly but should I add a news section? |
Sorry, something went wrong.
|
Yes, you should. it's a user-visible change. |
Sorry, something went wrong.
| assert(PyCode_Check(op)); | ||
| return op->co_nlocalsplus - op->co_nfreevars; | ||
| } | ||
|
|
There was a problem hiding this comment.
If the deprecation has no detail, for me, it can be removed as soon as in Python 3.15. But the doc is more specific:
"The old name is deprecated, but will remain available until the signature changes again."
Please add a comment to explain it here.
Sorry, something went wrong.
There was a problem hiding this comment.
If the deprecation has no detail, for me, it can be removed in Python 3.15.
What are you basing this on?
Sorry, something went wrong.
There was a problem hiding this comment.
PEP 387: Similarly a feature cannot be removed without notice between any two consecutive releases.
Sorry, something went wrong.
There was a problem hiding this comment.
I'm sorry, I didn't disable automerge after your comment. I didn't mean to ignore you :(
But IMO, the “Basic Policy” is just a summary. The “Making Incompatible Changes” section has more detailed instructions.
If you disagree with my reading, let's take it to Discourse; this isn't a good place for it.
Sorry, something went wrong.
There was a problem hiding this comment.
It's just that this function has a specific comment in the doc, IMO it's worth it to repeat it in the header to avoid future eagger removal. But well, now that the change is merged, it's maybe no longer worth it.
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
According to this , should I mention it in the documentation in a separate pull request?