Re: [Python-Dev] Issue #26204: compiler now emits a SyntaxWarning on constant statement

[xiscu]

>> New behaviour:
>>
>> haypo@smithers$ ./python
>> Python 3.6.0a0 (default:759a975e1230, Feb  8 2016, 18:21:23)
> def f():
>> ...  False
>> ...

Ok, I see in your case there's no return :-)

___
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] Accepting PEP 3154 for 3.4?

[xiscu]

Food for thought: maybe we should have variable-encoding lengths for 
all opcodes, rather than the current cumbersome scheme?



Funny, it sounds like UTF-8 :-)

___
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] Hg: inter-branch workflow

[xiscu]

On 03/21/2011 11:35 PM, "Martin v. Löwis" wrote:


If people then complain about too much fine-grainedness, we could
tighten it again.
   


Hi to all for the first time,

I'm new to this list. First of all I would like to thank all you for the 
great software and ideas you produce.


I found this thread of discussion interesting and well, it's just an idea:

Why not to TAG the final feature ? May be in a “parsable”, standard form ?

Ej:

>> hg tag -m “Feature : Templates for code generation, status: Done”

So If one doesn't want to see the “in between”, a tag filter can be 
applied, or something similar …


Of course there are 2 types of info here: “private” and “public” and 
well, like in python, use some kind of “underline” for private names 
here (def _do_my_thing(self): pass)


May be can be somehow automated …

Cheers / Saludos

francis


___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com