[Python-Dev] Is adding support for os.PathLike an enhancement or bugfix? (original) (raw)
Terry Reedy tjreedy at udel.edu
Thu May 4 13:30:10 EDT 2017
- Previous message (by thread): [Python-Dev] Is adding support for os.PathLike an enhancement or bugfix?
- Next message (by thread): [Python-Dev] Is adding support for os.PathLike an enhancement or bugfix?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 5/4/2017 10:43 AM, Koos Zevenhoven wrote:
On Thu, May 4, 2017 at 4:19 AM, Terry Reedy <tjreedy at udel.edu> wrote:
What did not get done for 3.6 should be proposed for 3.7.
Anyone, feel free. The nightmare part is done, so this could be a case where a PR actually pays off in terms of being able to use the feature. There's no need for any unnecessary masochism (should there ever be?).
I have no idea what this means, but don't need to.
Enhancing public APIs in normal (non-provisional) modules in bugfix releases has turned out to be a bad thing to do. Hence the policy to not do that. The few exceptions have been necessary to fix a bug that needed to be fixed, and could not reasonably be fixed otherwise. Such exceptions can of course more easily be made when the adoption of a version is still small, and almost all users will never see X.Y.0 or X.Y.1.
This is not an allowed excuse for breaking the policy. The x.y language is defined when x.y.0 is released. Please stop.
-- Terry Jan Reedy
- Previous message (by thread): [Python-Dev] Is adding support for os.PathLike an enhancement or bugfix?
- Next message (by thread): [Python-Dev] Is adding support for os.PathLike an enhancement or bugfix?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]