>
> 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 mai
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
> stab
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 d
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 alr
On 17 October 2016 at 16:18, INADA Naoki wrote:
> (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
*
(Added python-dev in CC list, because there are enough +1 already).
On Mon, Oct 17, 2016 at 3:06 PM, Chris Angelico wrote:
> 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