[issue18615] sndhdr.whathdr could return a namedtuple

Claudiu Popa added the comment: Serhiy, if there's no actual gain in changing this, should we close the issue? -- ___ Python tracker ___ _

[issue19776] Provide expanduser() on Path objects

Claudiu Popa added the comment: Since all the comments have been addressed, it would be nice if this gets committed. -- stage: patch review -> commit review ___ Python tracker _

[issue20451] os.exec* mangles argv on windows (splits on spaces, etc)

Raymond Hettinger added the comment: > My vote is for leaving this alone and letting the higher level > functions be more clever. Changing this function is certain to > break existing code in unpredictable ways. That is sensible. Marking this as closed. -- resolution: -> wont fix sta

[issue21793] httplib client/server status refactor

Demian Brecht added the comment: Bump for a follow-up review or merge -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsu

[issue21588] Idle: make editor title bar user configurable

Terry J. Reedy added the comment: I decided that it would be better to try to quickly solve Raymond's issue with editor windows in a simpler fashion and not rush this. Once we add a new configuration option, the cross-version nature of user config files means we are more or less stuck with the

[issue17535] IDLE: Add an option to show line numbers along the left side of the editor window, and have it enabled by default.

Terry J. Reedy added the comment: I tried v2 and it works, subject to the following comments. 1. (The biggest issue) For me, the 'obvious' implementation would be a narrow text window using the same font and size as the main window. The canvas introduces the problem of having to calculate the

[issue21978] Support index access on OrderedDict views (e.g. o.keys()[7])

Raymond Hettinger added the comment: Closing this. The premise is flawed. Guido designed mapping views to be a pass-through to the underlying mapping. As such, they would only have sequence behavior if the underlying mapping had sequence behavior. The implementation of both regular dicts

[issue21984] list(itertools.repeat(1)) causes the system to hang

Raymond Hettinger added the comment: > Python has no mechanism for identifying the difference > between an infinitely long generator and a long but finite generator. > Eventually, if you left the code running, it should eventually > exhaust physical memory and the page file, then die with a Memo

[issue15443] datetime module has no support for nanoseconds

Alexander Belopolsky added the comment: If alignment is not required (as is the case in pickle), we can pack year through second + nanosecond fields in 9 bytes. For backwards compatibility we should continue accepting 10-byte pickles, but we can write in a new 9-byte format. --

[issue15443] datetime module has no support for nanoseconds

Alexander Belopolsky added the comment: > I suppose another possibility is to get rid of microseconds > internally, and work with a single 4-byte nanosecond member. Yes, that is what I think we should do. I would also split it from the packed fields to give it a 32-bit alignment which should i

[issue21982] Idle configDialog: fix regression and add minimal unittest

Terry J. Reedy added the comment: Thanks for catching this. Either I misread pyflakes output or it has a bug. In either case, I should have searched this one like I did some others. The htest caught this. I added a minimal unittest that initially failed, covers half the module, and now passes

[issue15443] datetime module has no support for nanoseconds

Alexander Belopolsky added the comment: The following code demonstrates that we can pack year through second fields in 40 bits: #include struct dt { unsigned year :14; /* 1- of 0-16,383 */ unsigned month :4; /* 1-12 of 0-16 */ unsigned day :5; /* 1-31 of 0-31 */ unsigned ho

[issue21982] Idle: Regression introduced in configDialog by rev 91509

Roundup Robot added the comment: New changeset af1351800c7a by Terry Jan Reedy in branch '2.7': Issue #21982: Add minimal unittest for configDialog with 46% coverage. http://hg.python.org/cpython/rev/af1351800c7a New changeset 681979c6e6b2 by Terry Jan Reedy in branch '3.4': Issue #21982: Add mi

[issue15443] datetime module has no support for nanoseconds

Tim Peters added the comment: Of course pickles come with overheads too - don't be tedious ;-) The point is that the guts of the datetime pickling is this: basestate = PyBytes_FromStringAndSize((char *)self->data, _PyDateTime_DATETIME_DATASIZE); That con

[issue15443] datetime module has no support for nanoseconds

Alexander Belopolsky added the comment: > Guessing Guido was actually thinking about the pickle size No, pickle also comes with an overhead >>> from datetime import * >>> import pickle >>> t = datetime.now() >>> len(pickle.dumps(t)) 70 For the present discussion, DATETIME_DATASIZE is the only

[issue8519] doc: termios and ioctl reference links

Guido van Rossum added the comment: In this case I think there is no legal issue. All you have to do is take the link from the patch and come up with a fresh patch of your own. (However I think Georg's objection against a Linux-specific link stands. You can probably find a POSIX link that woul

[issue15443] datetime module has no support for nanoseconds

Tim Peters added the comment: Yup, it's definitely more than 8 bytes. In addition to the comments you quoted, an in-memory datetime object also has a full Python object header, a member to cache the hash code, and a byte devoted to saying whether or not a tzinfo member is present. Guessing G

[issue15443] datetime module has no support for nanoseconds

Antoine Pitrou added the comment: Le 14/07/2014 21:37, Alexander Belopolsky a écrit : > > AFAIK, Python objects are allocated with at least 32-bit alignment, 64 bits, actually, when using obmalloc.c. -- ___ Python tracker

[issue15443] datetime module has no support for nanoseconds

Alexander Belopolsky added the comment: > (there's no room for an extra 10 bits in the > carefully arranged 8-byte internal representation) According to a comment on top of Include/datetime.h, the internal representation of datetime is 10, not 8 bytes. /* Fields are packed into successive byt

[issue20117] subprocess on Windows: wrong return code with shell=True

eryksun added the comment: For what it's worth, an explicit "exit" will set the return code to the last error. >>> subprocess.call("nonex & exit", shell=True, stderr=subprocess.DEVNULL) 9009 -- nosy: +eryksun ___ Python tracker <

[issue15443] datetime module has no support for nanoseconds

Tim Peters added the comment: A note from Guido, from about 2 years ago: https://mail.python.org/pipermail/python-dev/2012-July/121127.html """ TBH, I think that adding nanosecond precision to the datetime type is not unthinkable. You'll have to come up with some clever backward compatibility i

[issue21815] imaplib truncates some untagged responses

Lita Cho added the comment: I was reading the RFC spec, and it looks like it doesn't specificy '[' and ']' are not allowed in the PERNANENTFLAGS names. I can try to add a fix for this. But if anyone else knows if you are not allowed to have '[' or ']' in flag names, please let me know. -

[issue21983] segfault in ctypes.cast

eryksun added the comment: You need to cast to a pointer type, i.e. POINTER(Struct). Trying to cast to just Struct should raise a TypeError. Instead this revealed a bug in cast_check_pointertype (3.4.1): http://hg.python.org/cpython/file/c0e311e010fc/Modules/_ctypes/_ctypes.c#l5225 dict->prot

[issue15443] datetime module has no support for nanoseconds

Alexander Belopolsky added the comment: numpy's datetime64 and timedelta64 types are so utterly broken that I would only recommend studying them as a negative example of how not to design a date-time library. -- ___ Python tracker

[issue21976] Fix test_ssl.py to handle LibreSSL versioning appropriately

Antoine Pitrou added the comment: I don't have LibreSSL to test but the patch sounds fine to me. -- ___ Python tracker ___ ___ Python-

[issue15443] datetime module has no support for nanoseconds

Antoine Pitrou added the comment: For the record, numpy's datetime and timedelta types have theoretical support for attoseconds. -- nosy: +pitrou ___ Python tracker ___

[issue21984] list(itertools.repeat(1)) causes the system to hang

Josh Rosenberg added the comment: It's unlikely to have hung the system entirely. It will slow down a lot though, as it will consume ridiculous amounts of RAM, and occasionally involve copying the existing data due to reallocation. The cost of performing this pointless work may consume enough

[issue21815] imaplib truncates some untagged responses

Changes by Lita Cho : -- nosy: +Lita.Cho, jesstess ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail

[issue17390] display python version on idle title bar

Terry J. Reedy added the comment: I agree that the repeated 'Python x.y.z: " in the listing is too much. #21588 has a patch but I am not ready to push it or do the review and revision needed . So I propose to reduce the current prefix to the minimum needed to know what version F5 will run the

[issue21984] list(itertools.repeat(1)) causes the system to hang

New submission from James Paget: In Python 3.4, type: >>> import itertools >>> list(itertools.repeat(1)) The system will hang, and a cold reboot is necessary (at least on Windows). I expected some sort of "infinite list" exception to be thrown. -- components: Extension Modules messag

[issue21983] segfault in ctypes.cast

Changes by Anthony LaTorre : -- components: +ctypes ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mai

[issue21983] segfault in ctypes.cast

New submission from Anthony LaTorre: I get a segfault when trying to cast a string to a structure. >>> import ctypes >>> class Struct(ctypes.Structure): ... _fields_ = [('a', ctypes.c_uint32)] ... >>> s = '0'*100 >>> ctypes.cast(s,Struct) Segmentation fault The docs (https://docs.python.or

[issue18397] Python with MinGW

Mark Lawrence added the comment: Nothing has been done with #17605 or the associated issues to my knowledge. I've no idea as to whether or not the originator will be picking them up again or if he is open to another user picking them up. I do know that there are 56 open issues with mingw in

[issue16895] Batch file to mimic 'make' on Windows

Zachary Ware added the comment: Still relevant, but the current patch is overkill (Brian was right, it's just way more batch than is healthy to check in). Things are changing rapidly, though; I'll close it as "postponed" for now, with the expectation of reopening someday. -- assignee

[issue21041] pathlib.PurePath.parents rejects negative indexes

Mark Lawrence added the comment: #7951 has an interesting debate on negative indexes that is possibly applicable here. -- nosy: +BreamoreBoy ___ Python tracker ___ _

[issue15552] gettext: if looking for .mo in default locations, also look in locale-bundle location

Mark Lawrence added the comment: @Dominique please accept our apologies for the delay in replying. Can someone please review the attached patch as it's only five extra lines. I'd do it myself but I know nothing about openSUSE, internationalization or gettext. -- nosy: +BreamoreBoy _

[issue17250] argparse: Issue 15906 patch; positional with nargs='*' and string default

Mark Lawrence added the comment: Slipped under the radar? -- nosy: +BreamoreBoy ___ Python tracker ___ ___ Python-bugs-list mailing li

[issue15117] Please document top-level sqlite3 module variables

Mark Lawrence added the comment: @wchlm sorry about the delay in responding, but would you like to propose a patch for this? -- nosy: +BreamoreBoy ___ Python tracker ___ ___

[issue14379] Several traceback docs improvements

Mark Lawrence added the comment: As nobody has even commented on this, let alone proposed a patch, I'd be inclined to close as "won't fix" or "out of date". -- nosy: +BreamoreBoy ___ Python tracker ___

[issue21041] pathlib.PurePath.parents rejects negative indexes

akira added the comment: > Aren't negative indexes well defined in Python? yes. I've provided the link to Python docs [1] in msg214642 that explicitly defines the behavior: > If i or j is negative, the index is relative to the end of the string: > len(s) + i or len(s) + j is substituted. Bu

[issue12955] urllib.request example should use "with ... as:"

Changes by Terry J. Reedy : -- versions: +Python 3.4, Python 3.5 -Python 3.2, Python 3.3 ___ Python tracker ___ ___ Python-bugs-list m

[issue21645] test_read_all_from_pipe_reader() of test_asyncio hangs on FreeBSD 9

STINNER Victor added the comment: Buildbot where the issue occurs: http://buildbot.python.org/all/builders/AMD64%20FreeBSD%209.0%203.x/ -- ___ Python tracker ___

[issue21645] test_read_all_from_pipe_reader() of test_asyncio hangs on FreeBSD 9

Roundup Robot added the comment: New changeset dbf991650441 by Victor Stinner in branch 'default': Issue #21645: test_asyncio, log debug trace into sys.__stderr__, not in http://hg.python.org/cpython/rev/dbf991650441 -- ___ Python tracker

[issue21514] update json module docs in light of RFC 7159 & ECMA-404

Changes by Bob Ippolito : -- assignee: bob.ippolito -> rhettinger ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe

[issue21514] update json module docs in light of RFC 7159 & ECMA-404

Raymond Hettinger added the comment: Thanks Bob. If you want me to apply the patch, just assign this back to me. -- ___ Python tracker ___ __

[issue21981] Idle problem

Terry J. Reedy added the comment: Thomas, PLEASE stop quoting messages when you post by email. Use your mouse selection and delete key. There is an open issue for adding lines numbers in the editor: #17535. It has a patch waiting for review. The bug you reported has not been fixed. Silent Gho

[issue21976] Fix test_ssl.py to handle LibreSSL versioning appropriately

Changes by Antoine Pitrou : -- stage: -> patch review ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://

[issue21645] test_read_all_from_pipe_reader() of test_asyncio hangs on FreeBSD 9

Roundup Robot added the comment: New changeset a0e6a370755f by Victor Stinner in branch 'default': Issue #21645: Add debug code to analyze a failure on FreeBSD 9 http://hg.python.org/cpython/rev/a0e6a370755f -- ___ Python tracker

[issue2698] Extension module build fails for MinGW: missing vcvarsall.bat

Changes by Mark Lawrence : -- nosy: +eric.araujo ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.py

[issue21041] pathlib.PurePath.parents rejects negative indexes

Barry A. Warsaw added the comment: Aren't negative indexes well defined in Python? E.g. >>> p = Path('/tmp/tmp123/foo/bar/baz.xz') >>> p.parents[len(p.parents)-2] PosixPath('/tmp') p.parents[-2] should == p.parents[len(p.parents)-2] -- ___ Python t

[issue16807] argparse group nesting lost on inheritance

paul j3 added the comment: To put this issue in perspective: - There's nothing in the documentation about nesting a mutually exclusive group in an argument group. - There are prominent notes in the documentation about MEGs not taking title and description. The '_add_container_actions' code h

[issue21041] pathlib.PurePath.parents rejects negative indexes

Changes by Barry A. Warsaw : -- nosy: +barry ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pytho

[issue21980] Implement `logging.LogRecord.__repr__`

Ram Rachum added the comment: Sounds good. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pyth

[issue21980] Implement `logging.LogRecord.__repr__`

New submission from Vinay Sajip: LogRecord has a lot of attributes. You can normally show what you want using a Formatter. I could implement something that just shows name and levelName. How does that sound? -- ___ Python tracker

[issue21922] PyLong: use GMP

Mark Dickinson added the comment: > When GMP encounters a memory allocation failure (exceeding the limits above > or when running our of scratch space), it will just abort. Ouch; that's not friendly. Seems like this is part of the reason that Armin Rigo abandoned the attempt to use GMP in PyP

[issue21956] Doc files deleted from repo are not deleted from docs.python.org.

Brandon Rhodes added the comment: Now that I am back at a full keyboard, I see that my previous response to @BreamoreBoy about this issue is too short and too cryptic to really serve as a fair answer to his question. And, with some embarrassment, I note that my words did not even achieve the dig

[issue15443] datetime module has no support for nanoseconds

Alexander Belopolsky added the comment: Given that struct timespec defined as struct timespec { time_t tv_sec;/* seconds */ long tv_nsec; /* nanoseconds */ }; is slowly becoming the prevailing standard to represent time in

[issue21514] update json module docs in light of RFC 7159 & ECMA-404

Bob Ippolito added the comment: Good call, I was just doing a quick review of the patch in isolation. Now I don't have anything at all to comment on :) -- ___ Python tracker ___

[issue21514] update json module docs in light of RFC 7159 & ECMA-404

Chris Rebert added the comment: Thanks for the speedy review! Those NaN-related arguments are already mentioned in the docs (see last 2 sentences of https://docs.python.org/3/library/json.html#infinite-and-nan-number-values ), and this patch doesn't touch that subsection. -- ___

[issue15443] datetime module has no support for nanoseconds

Niklas Claesson added the comment: I would like to add a use case. Control systems for particle accelerators. We have ns, sometimes ps precision on timestamped data acquisitions and we would like to use Python to do calculations. -- nosy: +Niklas.Claesson _

[issue21514] update json module docs in light of RFC 7159 & ECMA-404

Bob Ippolito added the comment: This patch looks reasonable to me as-is. With regard to "Infinite and NaN number values are accepted and output;" there's an option for that (allow_nan=False in encoding, parse_constant=some_function_that_raises in decoding). Since an exception can't be raised

[issue7834] socket.connect() no longer works with AF_BLUETOOTH L2CAP sockets

Changes by Tim Tisdall : -- nosy: +Tim.Tisdall ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pyth

[issue7687] Bluetooth support untested

Changes by Brian Curtin : -- nosy: -brian.curtin ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.p

[issue7687] Bluetooth support untested

Changes by Tim Tisdall : -- nosy: +Tim.Tisdall ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pyth

[issue17056] Support Visual Studio 2012

Steve Dower added the comment: msvc9compiler should not look for any versions of MSVC other than 9.0, since extensions built using other versions will be subtly (or dramatically) incompatible with Python unless you also rebuild Python itself with the same MSVC version. You can set DISTUTILS_U

[issue15883] Add Py_errno to work around multiple CRT issue

Steve Dower added the comment: Also agreed with not exposing a side-channel to set errno. I'd expect this to no longer be an issue with the stable CRT, but I'm not 100% confident about saying that yet. In theory, there will only ever be one CRT loaded in the future, but there's probably going

[issue20451] os.exec* mangles argv on windows (splits on spaces, etc)

Steve Dower added the comment: Automatically quoting arguments is more complicated than simply concatenating quotes, unfortunately, and people are guaranteed to have come up with ways to make it work already. My vote is for leaving this alone and letting the higher level functions be more cle

[issue17480] pyvenv should be installed someplace more obvious on Windows

Steve Dower added the comment: That last message should have been on #20451 :) My thoughts on pyvenv are that it should be in Scripts\ if anywhere, but I'm not desperate to have it on PATH. I would rather not start putting more files alongside python.exe. -- _

[issue17480] pyvenv should be installed someplace more obvious on Windows

Steve Dower added the comment: Automatically quoting arguments is more complicated than simply concatenating quotes, unfortunately, and people are guaranteed to have come up with ways to make it work already. My vote is for leaving this alone and letting the higher level functions be more cle

[issue21976] Fix test_ssl.py to handle LibreSSL versioning appropriately

Changes by Berker Peksag : -- nosy: +christian.heimes, dstufft, giampaolo.rodola, pitrou versions: -Python 3.1, Python 3.2, Python 3.3 ___ Python tracker ___ ___

[issue21980] Implement `logging.LogRecord.__repr__`

Changes by Berker Peksag : -- nosy: +vinay.sajip ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.p

[issue21977] In the re's token example OP and SKIP regexes can be improved

Changes by Berker Peksag : -- stage: commit review -> resolved ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue16561] bdist_wininst installers don't use UAC, then crash

Changes by Steve Dower : -- nosy: +steve.dower ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pyt

[issue16561] bdist_wininst installers don't use UAC, then crash

Martin v. Löwis added the comment: I just noticed that I misread the original issue: it's not about the Python Windows installer, but about bdist_wininst packages. -- title: Windows installer doesn't use UAC, then crashes -> bdist_wininst installers don't use UAC, then crash _

[issue21982] Idle: Regression introduced in configDialog by rev 91509

Changes by Saimadhav Heblikar : -- type: -> crash ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail

[issue21982] Idle: Regression introduced in configDialog by rev 91509

New submission from Saimadhav Heblikar: The concerned part : http://hg.python.org/cpython/rev/b836a0cd68f7#l4.15 "NameError: name 'keySet' is not defined." -- messages: 223031 nosy: sahutd, terry.reedy priority: normal severity: normal status: open title: Idle: Regression introduced in

[issue21947] `Dis` module doesn't know how to disassemble generators

Clement Rouault added the comment: Updated some docstrings in the new patch after the review comments. Thanks kushou for the code review. -- Added file: http://bugs.python.org/file35954/dis_generator3.patch ___ Python tracker

[issue21975] Using pickled/unpickled sqlite3.Row results in segfault rather than exception

Claudiu Popa added the comment: Ups, I accidentally removed the patch review stage, sorry for that. -- stage: -> patch review ___ Python tracker ___

[issue21981] Idle problem

Thomas Kember added the comment: Hello Eric V. Smith, I reported only one bug and it has been fixed. I can't find out how I am to reset the status of it to closed. Thomas Kember From: Eric V. Smith To: t.kemb...@btinternet.com Sent: Monday, 14 July 2014, 13

[issue21964] inconsistency in list-generator comprehension with yield(-from)

hakril added the comment: I found something else, I think it worth mentioning it. This side-effect allows to create generators that return other values that None. And the CPython's behavior is not the same for all versions: >>> {(yield i) : i for i in range(2)} at 0x7f0b98f41410>

[issue8849] python.exe problem with cvxopt

R. David Murray added the comment: True. Since there was no response from the OP to my question, let's close this. It can be reopened if he's still having a problem, which seems unlikely. -- resolution: -> third party stage: -> resolved status: open -> closed type: -> behavior ___

[issue21975] Using pickled/unpickled sqlite3.Row results in segfault rather than exception

Serhiy Storchaka added the comment: For pickling open other issue. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubsc

[issue19806] smtpd crashes when a multi-byte UTF-8 sequence is split between consecutive data packets

R. David Murray added the comment: As Milan said, the problem doesn't arise in 3.5 with decode_data=False, since there's no decoding. His patch doesn't actually fix the bug for the decode_data=True case, though, since the bug is a *valid* utf-8 sequence getting split across tcp buffers. To f

[issue21975] Using pickled/unpickled sqlite3.Row results in segfault rather than exception

Claudiu Popa added the comment: It doesn't crash anymore with your patch, but the pickle.load fails: Traceback (most recent call last): File "a.py", line 19, in load = pickle.loads(dump) TypeError: function takes exactly 2 arguments (0 given) -- stage: patch review -> _

[issue21975] Using pickled/unpickled sqlite3.Row results in segfault rather than exception

Serhiy Storchaka added the comment: Here is a patch which fixes crash. -- stage: -> patch review Added file: http://bugs.python.org/file35953/sqlite3_row_new.patch ___ Python tracker __

[issue21975] Using pickled/unpickled sqlite3.Row results in segfault rather than exception

Claudiu Popa added the comment: Nevermind, I didn't see the len call. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsu

[issue21975] Using pickled/unpickled sqlite3.Row results in segfault rather than exception

Claudiu Popa added the comment: Using your example, I can't make it to crash using the tip, nor with Python 3.4. -- ___ Python tracker ___ ___

[issue21981] Idle problem

Eric V. Smith added the comment: Please respond to the other bug. No need to open a new bug when responding to an existing issue. Thanks. -- nosy: +eric.smith resolution: -> not a bug stage: -> resolved status: open -> closed ___ Python tracker

[issue21981] Idle problem

Changes by SilentGhost : -- nosy: +terry.reedy ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pyt

[issue21979] SyntaxError not raised on "0xaor 1"

Mark Dickinson added the comment: > Mark, can you explain why the first example is valid syntax, but the second > one is not: Looks like Eric beat me to it! As he explained, it's the "maximal munch" rule at work: the tokenizer matches as much as it can for each token. You see similar effects

[issue21981] Idle problem

New submission from Thomas Kember: Hello Terry, Thank you for your explanation of the bug in Idle. I know Idle has limitations, but it is quite adequate for the programming I want to do. I agree that when this error occurs there should only be a warning, so the user can decide what he wants t

[issue21975] Using pickled/unpickled sqlite3.Row results in segfault rather than exception

Serhiy Storchaka added the comment: The issue is not in pickling/unpickling, but in sqlite3.Row.__new__ which creates object in invalid state. Simple example: >>> import sqlite3 >>> r = sqlite3.Row.__new__(sqlite3.Row) >>> len(r) Segmentation fault (core dumped) -- assignee: -> serhiy

[issue21980] Implement `logging.LogRecord.__repr__`

Changes by Ram Rachum : -- components: Library (Lib) nosy: cool-RR priority: normal severity: normal status: open title: Implement `logging.LogRecord.__repr__` type: enhancement versions: Python 3.5 ___ Python tracker

[issue21979] SyntaxError not raised on "0xaor 1"

Eric V. Smith added the comment: To be more clear: the parser takes the longest token that could be valid. Since "n" can't be part of a hex number, parsing stops there, returning "0xaa" as the first token. So: >>> 0xaaif 1 else 0 170 >>> hex(0xaaif 1 else 0) '0xaa' >>> -- __

[issue21979] SyntaxError not raised on "0xaor 1"

Mika Eloranta added the comment: OK, I see... "0xfand 1" is ambiguous "(0xfa)nd 1" vs. "(0xf)and 1". So, while a bit weird, the behavior is consistent: >>> 123not in [], 0xfnot in [], 0xfor 1, 0xafor 1, 0xfin [] (True, True, 15, 175, False) -- ___ P

[issue21979] SyntaxError not raised on "0xaor 1"

Changes by Eric V. Smith : -- stage: -> resolved ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.

[issue21979] SyntaxError not raised on "0xaor 1"

Eric V. Smith added the comment: 0xaand 1 is parsed as 0xaa nd 1 which is not valid syntax. -- nosy: +eric.smith ___ Python tracker ___ _

[issue21979] SyntaxError not raised on "0xaor 1"

Mika Eloranta added the comment: Mark, can you explain why the first example is valid syntax, but the second one is not: >>> 0xaor 1 10 >>> 0xaand 1 File "", line 1 0xaand 1 ^ SyntaxError: invalid syntax I do understand how "0xaor 1" is currently parsed, but I'm not still conv

[issue21979] SyntaxError not raised on "0xaor 1"

Mark Dickinson added the comment: Surprisingly, this is valid syntax. Your first line is parsed as: 0xf or (python is weird in ways) Because `or` is short-circuiting, its right-hand operand (which is also valid syntactically, being a chained comparison) is never evaluated, so we don't see

[issue21979] SyntaxError not raised on "0xaor 1"

New submission from Mika Eloranta: The following are expected to raise SyntaxError, but they don't: >>> 0xfor python is weird in ways 15 >>> [0xaor 1, 0xbor 1, 0xcor 1, 0xdor 1, 0xeor 1, 0xfor 1] [10, 11, 12, 13, 14, 15] Verified on v2.7.1 and v3.3.2. Probably affects all versions. --

  1   2   >