Re: [Python-Dev] Unicode exception indexing
> Is it worth the hassle? We can just port our existing error handlers, > and I guess the few third-party error handlers written in C (if any) > can bear the transition. That was my question exactly. As the author of PEP 393, I was leaning towards full backwards compatibility, but you, Victor, and Guido tell me not to worry - so I won't :-) Regards, Martin ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Unicode exception indexing
"Martin v. Löwis", 04.11.2011 08:39: Is it worth the hassle? We can just port our existing error handlers, and I guess the few third-party error handlers written in C (if any) can bear the transition. That was my question exactly. As the author of PEP 393, I was leaning towards full backwards compatibility, but you, Victor, and Guido tell me not to worry - so I won't :-) +1, FWIW. Stefan ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Code cleanups in stable branches?
Nick and Brett share the opinion that some code cleanups can be considered bugfixes, whereas MvL, Barry and Raymond defend that we never know what can get broken and it’s not worth risking it. I have added a comment on #13283 (removal of two unused variable in locale.py) to restate this policy, but haven’t asked for a revert; I did not comment on #10519 (Avoid unnecessary recursive function calls), as it can be considered a bugfix and Raymond took part in the discussion and thus implicitly approved the change. Regards ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] Summary of Python tracker Issues
ACTIVITY SUMMARY (2011-10-28 - 2011-11-04)
Python tracker at http://bugs.python.org/
To view or respond to any of the issues listed below, click on the issue.
Do NOT respond to this message.
Issues counts and deltas:
open3118 (+10)
closed 22006 (+45)
total 25124 (+55)
Open issues with patches: 1324
Issues opened (42)
==
#12119: test_distutils failure
http://bugs.python.org/issue12119 reopened by eric.araujo
#12342: characters with ord above 65535 fail to display in IDLE
http://bugs.python.org/issue12342 reopened by flox
#13290: get vars for object with __slots__
http://bugs.python.org/issue13290 opened by JBernardo
#13292: missing versionadded for bytearray
http://bugs.python.org/issue13292 opened by flox
#13294: http.server - HEAD request when no resource is defined.
http://bugs.python.org/issue13294 opened by karlcow
#13297: xmlrpc.client could accept bytes for input and output
http://bugs.python.org/issue13297 opened by flox
#13298: Result type depends on order of operands for bytes and bytearr
http://bugs.python.org/issue13298 opened by ncoghlan
#13299: namedtuple row factory for sqlite3
http://bugs.python.org/issue13299 opened by ncoghlan
#13300: IDLE 3.3 Restart Shell command fails
http://bugs.python.org/issue13300 opened by ned.deily
#13301: the script Tools/i18n/msgfmt.py allows arbitrary code executio
http://bugs.python.org/issue13301 opened by izi
#13302: Clarification needed in C API arg parsing
http://bugs.python.org/issue13302 opened by sandro.tosi
#13303: Sporadic importlib failures: FileNotFoundError on os.rename()
http://bugs.python.org/issue13303 opened by haypo
#13305: datetime.strftime("%Y") not consistent for years < 1000
http://bugs.python.org/issue13305 opened by flox
#13306: Add diagnostic tools to importlib?
http://bugs.python.org/issue13306 opened by ncoghlan
#13309: test_time fails: time data 'LMT' does not match format '%Z'
http://bugs.python.org/issue13309 opened by flox
#13311: asyncore handle_read should call recv
http://bugs.python.org/issue13311 opened by xdegaye
#13312: test_time fails: strftime('%Y', y) for negative year
http://bugs.python.org/issue13312 opened by flox
#13313: test_time fails: tzset() do not change timezone
http://bugs.python.org/issue13313 opened by flox
#13314: ImportError ImportError: Import by filename, should be deferre
http://bugs.python.org/issue13314 opened by Rob.Bairos
#13316: build_py_2to3 does not convert when there was an error in the
http://bugs.python.org/issue13316 opened by simohe
#13317: building with 2to3 generates wrong import paths because build_
http://bugs.python.org/issue13317 opened by simohe
#13319: IDLE: Menu accelerator conflict between Format and Options
http://bugs.python.org/issue13319 opened by serwy
#13320: _remove_visual_c_ref in distutils.msvc9compiler causes DLL loa
http://bugs.python.org/issue13320 opened by Inverness
#13321: fstat doesn't accept an object with "fileno" method
http://bugs.python.org/issue13321 opened by anacrolix
#13322: buffered read() and write() does not raise BlockingIOError
http://bugs.python.org/issue13322 opened by sbt
#13323: urllib2 does not correctly handle multiple www-authenticate he
http://bugs.python.org/issue13323 opened by dfischer
#13325: no address in the representation of asyncore dispatcher after
http://bugs.python.org/issue13325 opened by xdegaye
#13326: make clean failed on OpenBSD
http://bugs.python.org/issue13326 opened by rpointel
#13327: Update utime API to not require explicit None argument
http://bugs.python.org/issue13327 opened by brian.curtin
#13328: pdb shows code from wrong module
http://bugs.python.org/issue13328 opened by yak
#13329: Runs normal as console script but falls as CGI
http://bugs.python.org/issue13329 opened by Nick.Rowan
#13330: Attempt full test coverage of LocaleTextCalendar.formatweekday
http://bugs.python.org/issue13330 opened by Sean.Fleming
#13331: Packaging cannot install resource directory trees specified in
http://bugs.python.org/issue13331 opened by vinay.sajip
#13332: execfile fixer produces code that does not close the file
http://bugs.python.org/issue13332 opened by smarnach
#1: utf-7 inconsistent with surrogates
http://bugs.python.org/issue1 opened by pitrou
#13335: Service application hang in python25.dll
http://bugs.python.org/issue13335 opened by chandra
#13336: packaging.command.Command.copy_file doesn't implement preserve
http://bugs.python.org/issue13336 opened by vinay.sajip
#13337: IGNORE_CASE doctest option flag
http://bugs.python.org/issue13337 opened by Gerald.Dalley
#13338: Not all enumerations used in _Py_ANNOTATE_MEMORY_ORDER
http://bugs.python.org/issue13338 opened by flub
#13340: list.index does not accept None as start or stop
http://bugs.python.org/issue13340 opened by Carl.Friedrich.Bolz
#13341: Incorrect documentation for "u" PyArg_Parse format unit
http://bugs.python.org/issue13341 opened by I
Re: [Python-Dev] [Python-checkins] cpython: Port code page codec to Unicode API.
Le vendredi 4 novembre 2011 18:23:26, martin.v.loewis a écrit : > http://hg.python.org/cpython/rev/9191f804d376 > changeset: 73353:9191f804d376 > parent: 73351:2bec7c452b39 > user:Martin v. Löwis > date:Fri Nov 04 18:23:06 2011 +0100 > summary: > Port code page codec to Unicode API. Oh please, try to avoid introducing tabs when a file uses spaces. All C files are supposed to use an indentation of 4 spaces. Victor ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] [Python-checkins] cpython (2.7): Inline the advisory text on how to use the shelve module.
On 11/4/2011 4:08 PM, raymond.hettinger wrote: > - .. note:: > + Like file objects, shelve objects should closed explicitly to assure > + that the peristent data is flushed to disk. Missing "be" there, I think: "should be closed". Eric. ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] [Python-checkins] cpython (2.7): Inline the advisory text on how to use the shelve module.
On 04/11/2011 22.21, Eric V. Smith wrote: On 11/4/2011 4:08 PM, raymond.hettinger wrote: - .. note:: + Like file objects, shelve objects should closed explicitly to assure + that the peristent data is flushed to disk. Missing "be" there, I think: "should be closed". Eric. And on the next line it should be 'persistent'. Best Regards, Ezio Melotti ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] [Python-checkins] cpython (2.7): Inline the advisory text on how to use the shelve module.
On 11/4/2011 4:25 PM, Ezio Melotti wrote: > On 04/11/2011 22.21, Eric V. Smith wrote: >> On 11/4/2011 4:08 PM, raymond.hettinger wrote: >> >>> - .. note:: >>> + Like file objects, shelve objects should closed explicitly to assure >>> + that the peristent data is flushed to disk. >> Missing "be" there, I think: "should be closed". >> >> Eric. > > And on the next line it should be 'persistent'. And I'd argue that it should be "ensure" instead of "assure": you "ensure" an event occurs, you "assure" a person that it does. But it's a nit I wouldn't normally object to. Ezio is just making me re-read the sentence! Eric. ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Unicode exception indexing
On 11/4/2011 3:39 AM, "Martin v. Löwis" wrote: Is it worth the hassle? We can just port our existing error handlers, and I guess the few third-party error handlers written in C (if any) can bear the transition. That was my question exactly. As the author of PEP 393, I was leaning towards full backwards compatibility, but you, Victor, and Guido tell me not to worry - so I won't :-) While we need to keep the old api, I do not think we do not need to encourage its continued use by actively supporting it with new code. When 3.3 comes out, I think it should be socially OK to write C code only for 3.3+ by only using the new api. -- Terry Jan Reedy ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Packaging and binary distributions
On Sun, Oct 30, 2011 at 6:52 PM, Paul Moore wrote: > On 30 October 2011 18:04, Ned Deily wrote: > > Has anyone analyzed the current packages on PyPI to see how many provide > > binary distributions and in what format? > > A very quick and dirty check: > > dmg: 5 > rpm: 12 > msi: 23 > dumb: 132 > wininst: 364 > egg: 2570 > > That's number of packages with binary distributions in that format. > It's hard to be sure about egg distributions, as many of these could > be pure-python (there's no way I know, from the PyPI metadata, to > check this). > FYI, the egg filename will contain a distutils platform identifier (e.g. 'win32', 'macosx', 'linux', etc.) after the 'py2.x' tag if the egg is platform-specific. Otherwise, it's pure Python. ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Packaging and binary distributions
Urgh. I guess that was already answered. Guess this'll teach me not to reply to a thread before waiting for ALL the messages to download over a low-bandwidth connection... (am on the road at the moment and catching up on stuff in spare cycles - sorry for the noise) On Fri, Nov 4, 2011 at 10:24 PM, PJ Eby wrote: > On Sun, Oct 30, 2011 at 6:52 PM, Paul Moore wrote: > >> On 30 October 2011 18:04, Ned Deily wrote: >> > Has anyone analyzed the current packages on PyPI to see how many provide >> > binary distributions and in what format? >> >> A very quick and dirty check: >> >> dmg: 5 >> rpm: 12 >> msi: 23 >> dumb: 132 >> wininst: 364 >> egg: 2570 >> >> That's number of packages with binary distributions in that format. >> It's hard to be sure about egg distributions, as many of these could >> be pure-python (there's no way I know, from the PyPI metadata, to >> check this). >> > > FYI, the egg filename will contain a distutils platform identifier (e.g. > 'win32', 'macosx', 'linux', etc.) after the 'py2.x' tag if the egg is > platform-specific. Otherwise, it's pure Python. > > ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Code cleanups in stable branches?
On Sat, Nov 5, 2011 at 3:05 AM, Éric Araujo wrote: > Nick and Brett share the opinion that some code cleanups can be > considered bugfixes, whereas MvL, Barry and Raymond defend that we never > know what can get broken and it’s not worth risking it. > > I have added a comment on #13283 (removal of two unused variable in > locale.py) to restate this policy, but haven’t asked for a revert; I did > not comment on #10519 (Avoid unnecessary recursive function calls), as > it can be considered a bugfix and Raymond took part in the discussion > and thus implicitly approved the change. There's always going to be a grey area where it's a judgment call - my opinion is basically the same as what you state in your second paragraph. Cheers, Nick. -- Nick Coghlan | [email protected] | Brisbane, Australia ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
