On Wed, Jan 15, 2014 at 01:22:44PM +0100, Martin v. Löwis wrote:
Am 12.01.14 18:39, schrieb Nachshon David Armon:
I propose that this new version of python use the python 3 unicode model.
As the version of python will be fully compatible with both python 2 and
with python 3 but NOT
Am 12.01.14 18:39, schrieb Nachshon David Armon:
I propose that this new version of python use the python 3 unicode model.
As the version of python will be fully compatible with both python 2 and
with python 3 but NOT necsesarily with all existing code in either. It is
designed as a porting
On Wed, 15 Jan 2014 13:22:44 +0100
Martin v. Löwis mar...@v.loewis.de wrote:
Am 12.01.14 18:39, schrieb Nachshon David Armon:
I propose that this new version of python use the python 3 unicode model.
As the version of python will be fully compatible with both python 2 and
with python 3 but
On Wed, Jan 15, 2014 at 11:22 PM, Martin v. Löwis mar...@v.loewis.de wrote:
I don't think that it is possible to write an interpreter that is fully
compatible for all it accepts. Would you think that the program
print(repr(2**80).endswith(L))
is in the subset that should be supported by both
On 1/15/2014 8:21 AM, Chris Angelico wrote:
On Wed, Jan 15, 2014 at 11:22 PM, Martin v. Löwis mar...@v.loewis.de
wrote:
I don't think that it is possible to write an interpreter that is fully
compatible for all it accepts. Would you think that the program
print(repr(2**80).endswith(L))
is
15.01.14 14:22, Martin v. Löwis написав(ла):
I don't think that it is possible to write an interpreter that is fully
compatible for all it accepts. Would you think that the program
print(repr(2**80).endswith(L))
is in the subset that should be supported by both Python 2 and Python 3?
Notice
On Wed, 15 Jan 2014 16:31:17 +0200
Serhiy Storchaka storch...@gmail.com wrote:
15.01.14 14:22, Martin v. Löwis написав(ла):
I don't think that it is possible to write an interpreter that is fully
compatible for all it accepts. Would you think that the program
On Thu, Jan 16, 2014 at 1:25 AM, Eric V. Smith e...@trueblade.com wrote:
Easiest fix for that would be to have long.__repr__ omit the L tag.
Then it'll do the same as it would in Py3.
I think Martin's point is not this specific thing, but that such a
subset would be useless. Would you drop
15.01.14 16:34, Antoine Pitrou написав(ла):
If you explicitly create a long the L will always be printed:
long(0)
0L
Hey! long is not in common subset of Python 2 and Python 3.
___
Python-Dev mailing list
Python-Dev@python.org
https
On Wed, Jan 15, 2014 at 09:25:04AM -0500, Eric V. Smith wrote:
On 1/15/2014 8:21 AM, Chris Angelico wrote:
On Wed, Jan 15, 2014 at 11:22 PM, Martin v. Löwis mar...@v.loewis.de
wrote:
I don't think that it is possible to write an interpreter that is fully
compatible for all it accepts.
Hi,
I am Nachshon and this is my first post to the python mailing list.
I have been porting some libraries from python 2 to python 3 recently with
the goal of a common codebase that will run on both versions. I was
thinking it would make my life, and a lot of other developers as well, a
lot
Hi Nachson,
Python 2.7 with the -3 warning flag covers most of this, while using tox to
run automated tests under both 2.x and 3.x should cover the rest (tox is
also useful for checking code runs under Python 2.6, even if you normally
use a newer version).
Is there anything in particular you
On 12 Jan 2014 23:39, Nachshon David Armon nachshon.ar...@gmail.com
wrote:
Hi,
I am Nachshon and this is my first post to the python mailing list.
I have been porting some libraries from python 2 to python 3 recently
with the goal of a common codebase that will run on both versions. I was
On Sun, Jan 12, 2014 at 3:58 PM, Nick Coghlan ncogh...@gmail.com wrote:
On 12 Jan 2014 23:39, Nachshon David Armon nachshon.ar...@gmail.com
wrote:
I propose that this new version of python use the python 3 unicode model.
As the version of python will be fully compatible with both python 2
14 matches
Mail list logo
