Backward-incompatible change to random.randrange in 2.7.6
-----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-----
participants (12)
-
Antoine Pitrou
-
Barry Warsaw
-
Benjamin Peterson
-
Chris Angelico
-
Daniel Holth
-
Donald Stufft
-
Ethan Furman
-
Guido van Rossum
-
Nick Coghlan
-
Serhiy Storchaka
-
Tim Peters
-
Tres Seaver