User: Password:
|
|
Subscribe / Log in / New account

Backward-incompatible change to random.randrange in 2.7.6

From:  Tres Seaver <tseaver-AT-palladion.com>
To:  python-dev-AT-python.org
Subject:  Backward-incompatible change to random.randrange in 2.7.6
Date:  Tue, 17 Dec 2013 13:18:25 -0500
Message-ID:  <l8q4h5$ujb$1@ger.gmane.org>
Archive-link:  Article

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

http://hg.python.org/cpython/rev/b1e94e332ec8


Do we really want to change an undocumented-but-effectively-public API in
a late-in-the-release-cycle third dot release?  It caused, ZODB's tests
to fail, for instance.

While the docstring said, "Don't use the 'int', 'default', and 'maxwidth'
arguments", their names were not intrinsically private.  In particular,
passing in the 'int' argument was a strategy for generating compatible
long values when straddling Python 2.x / Python 3.x.




Tres.
- -- 
===================================================================
Tres Seaver          +1 540-429-0999          tseaver@palladion.com
Palladion Software   "Excellence by Design"    http://palladion.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlKwlXAACgkQ+gerLs4ltQ60DQCgzlO8mHMXQ0vsHNpS9GKwjpmD
G6oAoMIjtrKkGTlFj0b9Tfdj5BCu1rYS
=GxuS
-----END PGP SIGNATURE-----



(Log in to post comments)


Copyright © 2013, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds