Message280939
Per our conversation on IRC: since this is not a regression, it is unlikely to be addressed at this stage of the 3.6 release cycle. I'm adding the release manager as nosy just in case, but I don't expect him to want this to be addressed now.
IMO if the behavior does not match "the posix shell", then it is a bug, and can be fixed in 3.6.1. (I'd prefer not to wait longer than that, though). So proposing a patch with tests and doc changes would be beneficial.
As for the flag defaults, that's a backward compatibility issue. I don't like the idea of changing the default based on the value of another flag, but it could be discussed. The 'longer term' would be a several release deprecation cycle...I think that has been discussed previously but I can't find the discussion in a quick search. The documentation, however, could be improved. Please open a separate issue for the doc change request at least. |
|
Date |
User |
Action |
Args |
2016-11-16 12:32:21 | r.david.murray | set | recipients:
+ r.david.murray, vinay.sajip, eric.smith, robodan, ned.deily, ezio.melotti, eric.araujo, cvrebert, python-dev, Andrey.Kislyuk, evan_ |
2016-11-16 12:32:21 | r.david.murray | set | messageid: <1479299541.37.0.0147101082716.issue28595@psf.upfronthosting.co.za> |
2016-11-16 12:32:21 | r.david.murray | link | issue28595 messages |
2016-11-16 12:32:20 | r.david.murray | create | |
|