Clik here to view.
PEP 387: backwards compatibilty policy
native-api: t’s e.g. not impossible if stdlib incorporates a 3rd-party module – AFAIK multiprocessing is such a module Sure, but there is also a historical issue of trying to make things work when the...
View ArticlePEP 387: backwards compatibilty policy
I have made some changes based on feedback; see https://github.com/python/peps/commit/ac8b5c5f59e6ec2431adc1fe3398b9faedbad49 for those who are interested in only what changed. I have also updated the...
View ArticlePEP 387: backwards compatibilty policy
Possibly interesting for reference: https://twistedmatrix.com/documents/current/core/development/policy/compatibility-policy.html FWIW, it doesn’t declare behaviour such as side effects as something...
View ArticlePEP 387: backwards compatibilty policy
Reading the PEP, I can’t find an actual definition of what a backwards incompatibility is. Is it OK to implicitly rely on our shared intuition? Case in point: when...
View ArticleClik here to view.
PEP 387: backwards compatibilty policy
hawkowl: As an example, a static file serving resource takes a File to serve. A behaviour change of reading the whole file at once vs streaming it is inconsequential if the theoretical File object’s...
View ArticleClik here to view.
PEP 387: backwards compatibilty policy
brettcannon: encukou: Reading the PEP, I can’t find an actual definition of what a backwards incompatibility is . Is it OK to implicitly rely on our shared intuition? Yes. We are human beings and so...
View ArticlePEP 387: backwards compatibilty policy
See this discussion on python-dev for an example of where I suspect the PEP doesn’t provide clear enough guidance, and would need SC input. Personally, I’m a little concerned that there might be too...
View ArticlePEP 387: backwards compatibilty policy
People already become embroiled in arguments about backwards compatibility, and I don’t see why the acceptance of this PEP would worsen the situation. As Brett and others have said, we’ll never be...
View ArticlePEP 387: backwards compatibilty policy
Fair enough. I guess as long as people don’t start using the PEP as an argument for blocking changes without backing that up with a clarification of why they think the change breaks backward...
View ArticleClik here to view.
PEP 387: backwards compatibilty policy
pf_moore: I guess as long as people don’t start using the PEP as an argument for blocking changes without backing that up with a clarification of why they think the change breaks backward...
View ArticlePEP 387: backwards compatibilty policy
Regarding the (public) C-API, AFAIK we are already quite conservative in changes there, rarely break API compatibility, and mostly already follow PEP 387 (though the ability to emit deprecation...
View ArticleClik here to view.
PEP 387: backwards compatibilty policy
I’m scheduling the acceptance of this PEP in a week as things have settled down here and I believe the PEP addresses everyone’s concerns (and mine as PEP delegate ) . If you have a new concern which...
View ArticlePEP 387: backwards compatibilty policy
In case of C API, is runtime deprecation (e.g. raising DeprecationWarning) required, or is compiler warning enough? For example, PyLong_FromUnicode is deprecated at document since Python 3.3 and...
View ArticleClik here to view.
PEP 387: backwards compatibilty policy
methane: In case of C API, is runtime deprecation (e.g. raising DeprecationWarning) required, or is compiler warning enough? I would say the compiler warning is enough of a deprecation. methane: In my...
View ArticleClik here to view.
PEP 387: backwards compatibilty policy
github.com/python/peps Mention that C compiler warnings are acceptable notice for removal (#1464) committed 11:42PM - 24 Jun 20 UTC brettcannon +8 -7 Read full topic
View ArticleClik here to view.
PEP 387: backwards compatibilty policy
Thank you for updating the PEP. brettcannon: But if a compiler warning isn’t possible then I don’t think I agree you should skip the runtime warning. Yes, but I think it is still “best effort”, not a...
View ArticlePEP 387: backwards compatibilty policy
Compiler warnings are also acceptable. But compiler warnings are compiler-dependent, and AFAICS, Py_DEPRECATED doesn’t warn on all supported compilers. Isn’t that a problem? Read full topic
View ArticleClik here to view.
PEP 387: backwards compatibilty policy
encukou: Py_DEPRECATED doesn’t warn on all supported compilers. Is there a list of supported compilers? Py_DEPRECATED is implemented for gcc, clang, and msvc. It covers most extensions on PyPI. Read...
View ArticleClik here to view.
PEP 387: backwards compatibilty policy
encukou: But compiler warnings are compiler-dependent, and AFAICS, Py_DEPRECATED doesn’t warn on all supported compilers. Isn’t that a problem? I don’t think so. methane: Is there a list of supported...
View ArticleClik here to view.
PEP 387: backwards compatibilty policy
brettcannon: If someone chose to use an esoteric compiler and to never use a mainstream one to check for issues then that’s their choice, but I don’t see why it’s then our problem that the compiler...
View ArticleClik here to view.
PEP 387: backwards compatibilty policy
encukou: C compiler warnings are also acceptable: use Py_DEPRECATED or make sure the warning appears with all major compilers: gcc, clang and msvc. The problem with that statement is now PEP 387 is...
View ArticleClik here to view.
PEP 387: backwards compatibilty policy
brettcannon: The problem with that statement is now PEP 387 is suddenly dictating what the officially supported compilers of Python are. For compilation/behavior errors, a list of supported compilers...
View ArticleClik here to view.
PEP 387: backwards compatibilty policy
encukou: The section " Making Incompatible Changes, reads like a best practices checklist for contributors. IMO, “check more than just your own compiler” is a good step to add. Maybe it can be done...
View ArticlePEP 387: backwards compatibilty policy
The SC met today and we agreed to accept PEP 387! I just marked it as Active and will be sending out the announcement email shortly. Read full topic
View Article
