Re: [Python-Dev] [Python-ideas] Show more info when `python -vV`
> > I agree with Barry. I'm open to adding this feature to 3.6.0b3 but > first we need an issue and a final patch to review. > Here is the issue and patch. Could someone review it? http://bugs.python.org/issue28532 -- INADA Naoki___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] [Python-ideas] Show more info when `python -vV`
On 2016-10-17 15:05, Barry Warsaw wrote: > On Oct 17, 2016, at 05:01 PM, Nick Coghlan wrote: >> * Inada-san would like to enable "python -VV" to print the full REPL >> header for improved debugging information [...] > I'd personally have no problem with adding it to 3.6 and possibly earlier > stable releases, but I'm not an RM of any active releases any more. I'd say, > open a bug, post the patch against the versions you want to see it applied to, > go through the review process, and let the RMs decide if its worth the risk. I agree with Barry. I'm open to adding this feature to 3.6.0b3 but first we need an issue and a final patch to review. ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] [Python-ideas] Show more info when `python -vV`
It is a New Feature and therefore ineligible for adding to 3.5 or 3.4. //arry/ On 10/17/2016 08:05 PM, Barry Warsaw wrote: On Oct 17, 2016, at 05:01 PM, Nick Coghlan wrote: * Inada-san would like to enable "python -VV" to print the full REPL header for improved debugging information * we don't want to mess with "-V" because external scripts may be relying on it (e.g. to figure out filenames) * "python -VV" is already permitted, but just means the same thing as "python -V" I think this is a good idea So do I. , but this is a CPython-the-implementation feature, rather than a Python-the-language feature, so it isn't clear what rules apply to adding it. Certainly add it to 3.7. I think the decision whether to add it to 3.6 and the stable releases should be up to the respective release managers. As you say, it's not a language feature, but it's still a new feature and as such it does fall within a gray area. I'd personally have no problem with adding it to 3.6 and possibly earlier stable releases, but I'm not an RM of any active releases any more. I'd say, open a bug, post the patch against the versions you want to see it applied to, go through the review process, and let the RMs decide if its worth the risk. Cheers, -Barry ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/larry%40hastings.org ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] [Python-ideas] Show more info when `python -vV`
On Oct 17, 2016, at 05:01 PM, Nick Coghlan wrote: >* Inada-san would like to enable "python -VV" to print the full REPL >header for improved debugging information >* we don't want to mess with "-V" because external scripts may be >relying on it (e.g. to figure out filenames) >* "python -VV" is already permitted, but just means the same thing as >"python -V" > >I think this is a good idea So do I. >, but this is a CPython-the-implementation feature, rather than a >Python-the-language feature, so it isn't clear what rules apply to adding it. Certainly add it to 3.7. I think the decision whether to add it to 3.6 and the stable releases should be up to the respective release managers. As you say, it's not a language feature, but it's still a new feature and as such it does fall within a gray area. I'd personally have no problem with adding it to 3.6 and possibly earlier stable releases, but I'm not an RM of any active releases any more. I'd say, open a bug, post the patch against the versions you want to see it applied to, go through the review process, and let the RMs decide if its worth the risk. Cheers, -Barry ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] [Python-ideas] Show more info when `python -vV`
On 17 October 2016 at 16:18, INADA Naokiwrote: > (Added python-dev in CC list, because there are enough +1 already). (switching entirely to python-dev) Context for python-dev folks: * Inada-san would like to enable "python -VV" to print the full REPL header for improved debugging information * we don't want to mess with "-V" because external scripts may be relying on it (e.g. to figure out filenames) * "python -VV" is already permitted, but just means the same thing as "python -V" I think this is a good idea, but this is a CPython-the-implementation feature, rather than a Python-the-language feature, so it isn't clear what rules apply to adding it. As a pragmatic matter, I think it would be worth applying it to all active maintenance branches, as: - that dramatically reduces the deployment term for it to start being useful for troubleshooting - the SSL/TLS changes mean that some redistributed versions of Python 2.7 are starting to accumulate significant backports that aren't indicated in the nominal upstream version number, but are conveyed in the full REPL header (which has redistributor build info in it) Cheers, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] [Python-ideas] Show more info when `python -vV`
(Added python-dev in CC list, because there are enough +1 already). On Mon, Oct 17, 2016 at 3:06 PM, Chris Angelicowrote: > On Mon, Oct 17, 2016 at 5:02 PM, INADA Naoki wrote: >> $ ./python.exe -V >> Python 3.6.0b2+ >> >> $ ./python.exe -VV >> Python 3.6.0b2+ (3.6:0b29adb5c804+, Oct 17 2016, 15:00:12) >> [GCC 4.2.1 Compatible Apple LLVM 8.0.0 (clang-800.0.38)] > > LGTM. > > What's the view on backporting this to 2.7.x? We're still a good few > years away from its death, and it'd be helpful if recent 2.7s could > give this info too. > > ChrisA I want to add it at least Python 3.6. Because one reason I want to propose this is I can't see exact Python version (commit id) for "nightly" or "3.6-dev" on Travis-CI test. But Python 3.6 is beta stage already. If we apply rule strictly, it should be added only in default branch (Python 3.7). So, what version can I add this? a. Only Python 3.7+ b. (beta) Python 3.6+ c. (maintenance) Python 2.7 and Python 3.5+ -- INADA Naoki ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com