[issue10768] Bug in scrolledtext
New submission from Pierre Quentel pierre.quen...@gmail.com: The scrolledtext example crashes with this message : TypeError: unsupported operand type(s) for +: 'dict_keys' and 'dict_keys' It works if keys() are converted to lists in line 33 : methods = list(vars(Pack).keys()) + list(vars(Grid).keys()) + \list(vars(Place).keys()) Configuration : Python 3.2b2 (r32b2:87398, Dec 19 2010, 22:51:00) [MSC v.1500 32 bit (Intel)] on win32 -- components: Tkinter messages: 124593 nosy: quentel priority: normal severity: normal status: open title: Bug in scrolledtext type: crash versions: Python 3.2 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10768 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10763] subprocess.communicate() doesn't close pipes on Windows
Changes by Antoine Pitrou pit...@free.fr: -- nosy: +gps ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10763 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10768] Bug in scrolledtext
Daniel Urban urban.dani...@gmail.com added the comment: It probably also works if | is used instead of +, because in 3.2 dict_proxy.keys() are a dict_keys, not a list. See issue10630 . -- nosy: +durban ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10768 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10762] strftime('%f') segfault
David Leonard d+pyt...@adaptive-enterprises.com added the comment: Agree that the patches from issue 4804 and wrapping strftime() to catch the invalid_parameter call would fix this: windbg trace: 0:000 k Child-SP RetAddr Call Site `0021f328 07fe`fdbb27cf ntdll!ZwTerminateProcess+0xa `0021f330 `6ec24eec KERNELBASE!TerminateProcess+0x2f `0021f360 `6ec24fc0 MSVCR90!invoke_watson+0x11c `0021f950 `6ec11f5d MSVCR90!invalid_parameter+0x70 `0021f990 `6ec11fcd MSVCR90!Gettnames+0xebd `0021fa30 `1e062e29 MSVCR90!strftime+0x15 `0021fa70 `1e0bff79 python27!PyTime_DoubleToTimet+0x5f9 `0021fae0 `1e10f084 python27!PyCFunction_Call+0x69 `0021fb10 `1e112834 python27!PyEval_GetGlobals+0x944 `0021fb70 `1e114039 python27!PyEval_EvalFrameEx+0x36a4 `0021fc60 `1e1140d9 python27!PyEval_EvalCodeEx+0x7e9 `0021fd10 `1e1400ca python27!PyEval_EvalCode+0x29 `0021fd70 `1e1417f6 python27!PyErr_Display+0x40a `0021fda0 `1e14235e python27!PyRun_InteractiveOneFlags+0x1c6 `0021fe10 `1e1423d5 python27!PyRun_InteractiveLoopFlags+0xce `0021fe40 `1e0443d9 python27!PyRun_AnyFileExFlags+0x45 `0021fe70 `1d00119e python27!Py_Main+0x8e9 `0021ff30 `777bf56d python+0x119e `0021ff60 `779f3021 kernel32!BaseThreadInitThunk+0xd `0021ff90 ` ntdll!RtlUserThreadStart+0x21 -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10762 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10769] ast: provide more useful range information
New submission from Sven Brauch svenbra...@googlemail.com: Hi, I'm writing a python language support plugin for an IDE. I'm using the AST module to get information about the loaded source code, which works pretty well. However, in some cases, the information provided by the AST is simply not sufficient to do proper highlighting (or whatever); for example, class_instance.method(argument1.arg_attribute).attribute class_instance.method( argument1.arg_attribute). attribute and class_instance.method( argument1. \ arg_attribute) \ . attribute produce exactly the same syntax tree, making it impossible to determine where e.g. attribute starts and ends. Although technically obviously correct, the information that the column offset for attribute is 0 is quite pointless. It would really be great if there could be an additional attribute for Attribute Access nodes which tells me where the attribute access the node refers to *really* takes place, not just column 0. :) It would be even better if there was not only an offset, but also an end attribute providing information on where the node ends; that'd make this module way more useful, at least for me. Thanks and best regards, Sven -- components: Library (Lib) messages: 124596 nosy: georg.brandl, scummos priority: normal severity: normal status: open title: ast: provide more useful range information type: feature request ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10769 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6011] python doesn't build if prefix contains non-ascii characters
Baptiste Carvello baptiste...@free.fr added the comment: Hello, the patch solves the bug for me as well (using locale C, the filesystem encoding is utf-8). However, I do not understand why the patch checks that the shebang line decodes with both utf-8 and the file's encoding. The shebang line is only used by the kernel to locate the interpreter, so none of these should matter. Or have I misuderstood the patch? Cheers, Baptiste -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6011 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10769] ast: provide more useful range information
Changes by R. David Murray rdmur...@bitdance.com: -- nosy: +benjamin.peterson stage: - needs patch versions: +Python 3.3 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10769 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7198] Extraneous newlines with csv.writer on Windows
Skip Montanaro s...@pobox.com added the comment: John, The API for the open() builtin function has changed. You should open the output file with newline= instead of using the default. Take a look at the documentation for open() and csv.reader: http://docs.python.org/py3k/library/functions.html?highlight=open#open http://docs.python.org/py3k/library/csv.html?highlight=csv.reader#csv.reader Note the form of the open() call in the csv.reader example. This one snuck by me as well. Python 3 underwent a lot of change in the I/O subsystem. This was one of them. If changing the form of the open() call doesn't fix the problem, let me know. Skip -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7198 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10767] Lib/test/crashers/README is out of date
Brett Cannon br...@python.org added the comment: That's a fair assessment. A lot of the bugs that are easy to fix got closed out a couple of years back. The rest are (I think) considered too difficult and too marginal to worry about. -- nosy: +brett.cannon ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10767 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10770] zipinfo - fix of a typo in the doc
New submission from Sandro Tosi sandro.t...@gmail.com: Hello, as reported[1] on python-doc, there's a typo in zipinfo doc. [1] http://mail.python.org/pipermail/docs/2010-December/002526.html The attached (trivial) patch fixes it; the file would also need a rewrap to 80th column. Cheers, Sandro -- assignee: sandro.tosi components: Documentation files: zipinfo_typo.patch keywords: patch messages: 124600 nosy: sandro.tosi priority: low severity: normal stage: patch review status: open title: zipinfo - fix of a typo in the doc versions: Python 2.7, Python 3.1, Python 3.2 Added file: http://bugs.python.org/file20156/zipinfo_typo.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10770 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10769] ast: provide more useful range information
Raymond Hettinger rhettin...@users.sourceforge.net added the comment: ISTM the whole point of an Abstract Syntax Tree is to express semantics while throwing away the syntax details. The only reason any position information is kept is to support tracebacks and debugging. Perhaps the OP's request should changed to add function to concrete parse trees to show structure while preserving all the input detail returned by tokenize. -- nosy: +rhettinger ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10769 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10769] ast: provide more useful range information
Benjamin Peterson benja...@python.org added the comment: 2010/12/24 Raymond Hettinger rep...@bugs.python.org: Raymond Hettinger rhettin...@users.sourceforge.net added the comment: ISTM the whole point of an Abstract Syntax Tree is to express semantics while throwing away the syntax details. The only reason any position information is kept is to support tracebacks and debugging. I agree for the most part. It's also nearly impossible to preserve all the detail one would want in an *abstract* syntax tree. Perhaps the OP's request should changed to add function to concrete parse trees to show structure while preserving all the input detail returned by tokenize. If someone can comment on what that would look like... -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10769 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10769] ast: provide more useful range information
Raymond Hettinger rhettin...@users.sourceforge.net added the comment: If info fields are added, they need to be optional so that someone manipulating the tree (adding, rearranging, or removing nodes) doesn't have an additional burden of supplying this info before compiling into an executable code object. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10769 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10768] Bug in scrolledtext
R. David Murray rdmur...@bitdance.com added the comment: Where is this example? -- assignee: - d...@python components: +Documentation nosy: +d...@python, r.david.murray type: crash - behavior ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10768 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10768] Bug in scrolledtext
Daniel Urban urban.dani...@gmail.com added the comment: I don't think, that this is in an example (but probably there is an example somewhere, that crashes because of this). I found the code in Lib/tkinter/scrolledtext.py -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10768 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10626] Bad interaction between test_logging and test_concurrent_futures
Brian Quinlan br...@sweetapp.com added the comment:
Sorry for being AWOL for so long. Attached is a patch that doesn't install a
handler and checks stderr for the exception output. Unfortunately, it looks
like the logging tests are still messing things up:
./python.exe -m test test_concurrent_futures test_concurrent_futures
[1/2] test_concurrent_futures
[2/2] test_concurrent_futures
All 2 tests OK.
% ./python.exe -m test test_concurrent_futures test_logging
test_concurrent_futures
[1/3] test_concurrent_futures
[2/3] test_logging
[3/3] test_concurrent_futures
test test_concurrent_futures failed -- Traceback (most recent call last):
File /home/bquinlan/shared/py3k/Lib/test/test_concurrent_futures.py, line
642, in test_done_callback_raises
self.assertIn('Exception: doh!', stderr.getvalue())
AssertionError: 'Exception: doh!' not found in ''
2 tests OK.
1 test failed:
test_concurrent_futures
--
Added file: http://bugs.python.org/file20157/logging.patch
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10626
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9090] Error code 10035 calling socket.recv() on a socket with a timeout (WSAEWOULDBLOCK - A non-blocking socket operation could not be completed immediately)
Terry J. Reedy tjre...@udel.edu added the comment: 2.6 is closed except for security fixes, which this does not seem to be. If the problem is in 2.7, then it potentially could be fixed there, but with the same caveats. I will let Antoine reclose if he thinks appropriate. -- nosy: +terry.reedy stage: committed/rejected - patch review versions: +Python 2.7 -Python 2.6 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9090 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10733] plistlib rejects strings containing control characters
Terry J. Reedy tjre...@udel.edu added the comment: Mitchell: 2.6 is closed to revision except for security issues -- nosy: +terry.reedy resolution: wont fix - versions: +Python 3.2 -Python 2.6 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10733 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10768] Bug in scrolledtext
Changes by R. David Murray rdmur...@bitdance.com: -- assignee: d...@python - components: -Documentation keywords: +easy nosy: -d...@python stage: - unit test needed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10768 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10769] ast: provide more useful range information
Sven Brauch svenbra...@googlemail.com added the comment: Hi, well, but you have to agree that there is no point in setting a correct column offset for bar in foo[bar] (it's correctly set to 4 here!) and foo(bar) but not for foo.bar (there's no information provided here) For me, this looks like it was just done the easiest way -- which is okay, of course, but is not a valid reason not to change it now. It's also not that there's fifty things missing to make it fully functional for the purpose of highlighting / analyzing the code, this is about the only one. :) Best regards, Sven -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10769 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10738] webbrowser.py bug with Opera on Linux
Terry J. Reedy tjre...@udel.edu added the comment: According to the linked doc, Opera has '-noraise' but not '-raise' as a command line option (to not raise window when receiving remote commands). It does have 'raise()' (with quotes and parens, but not noraise()) as a remote command following the '-remote' command line option to be sent to another Opera window. I suspect this as the reason for the apparently invalid raise_opts = [, -raise] From the usage of raise_opts in UnixBrowser._invoke, which concatenates one of the entries, if not , to self.name, I am pretty sure the command line form is what is wanted and that the proposed raise_opts = [-noraise, ] is correct. Attached patch also removes a few blank lines to make entries for different browsers consistent. Georg, if you agree, I will commit the change and backport. -- keywords: +patch nosy: +terry.reedy stage: - commit review versions: +Python 3.1, Python 3.2 Added file: http://bugs.python.org/file20158/zweb.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10738 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10742] memoryview.readonly attribute is not documented
Terry J. Reedy tjre...@udel.edu added the comment: I agree with addition. Patch look OK to my limited .rst knowledge. To be more parallel to the other entries, the text might say A bool indicating whether ... -- nosy: +terry.reedy stage: - patch review versions: +Python 3.1, Python 3.2 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10742 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10756] Error in atexit._run_exitfuncs [...] Exception expected for value, str found
Changes by Terry J. Reedy tjre...@udel.edu: -- nosy: -BreamoreBoy ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10756 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10757] zipfile.write, arcname should be bytestring
Changes by Terry J. Reedy tjre...@udel.edu: -- nosy: +aimacintyre stage: - unit test needed type: compile error - behavior versions: +Python 3.2 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10757 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10762] strftime('%f') segfault
Terry J. Reedy tjre...@udel.edu added the comment: I verified problem with 3.2b1 on 32-bit winxp machine. IDLE restarts after pythonw crashes. -- nosy: +terry.reedy ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10762 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10737] test_concurrent_futures failure on Windows
Brian Quinlan br...@sweetapp.com added the comment: What's the best way for me to test this? The problem occurs on a Windows-only code path but there is not enough information for me to debug it. Should I check-in some additional diagnostics, wait for the buildbot to run, collect my data and then rollback my change? Or can I run code on the buildbot directly? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10737 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2636] Regexp 2.7 (modifications to current re 2.2.2)
Matthew Barnett pyt...@mrabarnett.plus.com added the comment: I've been trying to push the history to Launchpad, completely without success; it just won't authenticate (no such account, even though I can log in!). I doubt that the history would be much use to you anyway. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue2636 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10737] test_concurrent_futures failure on Windows
Brian Curtin cur...@acm.org added the comment: You can create a branch, checkin to that branch, then specify that a specific buildbot runs your branch. See the force build page of a build slave. Additionally, I can give you access to my build slave, the Windows Server 2008 one, but that may take a few days due to the holiday weekend. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10737 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9709] test_distutils warning: initfunc exported twice on Windows
Thorsten Behrens sbehr...@gmx.li added the comment: Thank you for that patch, Stefan. I am currently tinkering with bringing pycrypto to 3.x and ran into this issue. initfunc2.patch resolves the issue on Win7-64, python31-64. I don't feel comfortable releasing code that requires the user to manually patch Python to build. What are my options here? Go back to void instead of PyMODINIT_FUNC? Is there aught else I can do to make sure pycrypto will build well in the wild? -- nosy: +thorsten.behrens ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9709 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10733] plistlib rejects strings containing control characters
Changes by Terry J. Reedy tjre...@udel.edu: -- nosy: -terry.reedy ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10733 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1693546] email.Message set_param rfc2231 encoding incorrect
R. David Murray rdmur...@bitdance.com added the comment: No, I was wrong. This would only be an issue when a parameter's value is changed, and at that point we should be producing correctly (un)quoted values no matter what the original quoting of the individual value was. So I've applied the patch in r87479. -- resolution: - fixed stage: patch review - committed/rejected status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1693546 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10768] Bug in scrolledtext
Terry J. Reedy tjre...@udel.edu added the comment: Since 'methods' is converted to a set in the next line, there is no need for lists. Instead, use | and delete the conversion. methods = vars(Pack).keys() + vars(Grid).keys() + vars(Place).keys() methods = set(methods).difference(text_meths) becomes methods = vars(Pack).keys() | vars(Grid).keys() | vars(Place).keys() methods = methods.difference(text_meths) Now I am a little puzzled why this does not fail (3.2b1, winxp): from tkinter.scrolledtext import ScrolledText s = ScrolledText() s tkinter.scrolledtext.ScrolledText object at 0x00F6CF70 On the other hand, this fails elsewhere: from tkinter.scrolledtext import example example() Traceback (most recent call last): File pyshell#34, line 1, in module example() File C:\Programs\Python32\lib\tkinter\scrolledtext.py, line 49, in example stext.insert(END, __main__.__doc__) File C:\Programs\Python32\lib\tkinter\__init__.py, line 2970, in insert self.tk.call((self._w, 'insert', index, chars) + args) _tkinter.TclError: wrong # args: should be .16421456.16190896 insert index chars ?tagList chars tagList ...? -- nosy: +gpolo, terry.reedy versions: +Python 3.1 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10768 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10769] ast: provide more useful range information
Terry J. Reedy tjre...@udel.edu added the comment: A request limited only to fixing the current field for attribute may get more traction than a request for a new field. Can you dig into to code to get any idea why the difference between attributes versus indexes and parameters? -- nosy: +terry.reedy ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10769 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10769] ast: provide more useful range information
Sven Brauch svenbra...@googlemail.com added the comment: Hi Terry, well, the current behaviour is... logical in some way, as it says the whole expression which accesses an attribute starts at column 0, i.e. it's easy to understand why it's done like this. It just turns out that this is pretty useless... I'll try to find out what changes would be needed in the code to make the col_offset attribute useful in this case. Best regards, Sven -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10769 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7334] ElementTree: file locking in Jython 2.5 (OSError on Windows)
Philip Jenvey pjen...@underboss.org added the comment: Florent, any chance of signing off on this for 3.2? I was waiting for the patch to go through your authorized elementtree fork -- assignee: pjenvey - flox ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7334 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10737] test_concurrent_futures failure on Windows
Brian Quinlan br...@sweetapp.com added the comment: I'm good, thanks Brian C. br/ It looks like SetEvent is failing with ERROR_INVALID_HANDLE. CRITICAL:root:SetEvent(2044) failed with 0, GetLastError() = 6 CRITICAL:root:SetEvent(2064) failed with 0, GetLastError() = 6 CRITICAL:root:SetEvent(2220) failed with 0, GetLastError() = 6 CRITICAL:root:SetEvent(1576) failed with 0, GetLastError() = 6 CRITICAL:root:SetEvent(2284) failed with 0, GetLastError() = 6 CRITICAL:root:SetEvent(2168) failed with 0, GetLastError() = 6 CRITICAL:root:SetEvent(2264) failed with 0, GetLastError() = 6 CRITICAL:root:SetEvent(1588) failed with 0, GetLastError() = 6 CRITICAL:root:SetEvent(2240) failed with 0, GetLastError() = 6 Now to figure out why... -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10737 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10769] ast: provide more useful range information
Sven Brauch svenbra...@googlemail.com added the comment: Hi, I found the reason for this behavior in the code now, it's in Python/ast.c, lines 1745 and 1746 in ast_for_power(): tmp-lineno = e-lineno; tmp-col_offset = e-col_offset; Here, the range information for the individual attributes (which is correctly set before!) is being discarded and replaced by the useless information from the expression ast. I don't see any reason for this, is there one? :) Removing those two lines doesn't seem to break anything and sets ranges correctly. Best regards, Sven -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10769 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10769] ast: provide more useful range information
Benjamin Peterson benja...@python.org added the comment: 2010/12/24 Sven Brauch rep...@bugs.python.org: Sven Brauch svenbra...@googlemail.com added the comment: Hi, I found the reason for this behavior in the code now, it's in Python/ast.c, lines 1745 and 1746 in ast_for_power(): tmp-lineno = e-lineno; tmp-col_offset = e-col_offset; Here, the range information for the individual attributes (which is correctly set before!) is being discarded and replaced by the useless information from the expression ast. I don't see any reason for this, is there one? :) Removing those two lines doesn't seem to break anything and sets ranges correctly. The ranges are correct. They just aren't what you want. The attribute starts at the beginning of the power, not the .. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10769 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10733] plistlib rejects strings containing control characters
Mitchell Model m...@acm.org added the comment: Thanks for letting me know (and with a personalized message, yet!). I wasn't paying attention -- i verified that the problem exists in 2.7 and 3.1 and I just dragged 3.1 down to 2.6. Although I've been working furiously in Python for the past six months, I haven't been writing or teaching so I haven't been combing the documentation or testing examples or using obscure or forgotten features, which together are the source of nearly all my bug reports. So I just automatically did what I used to do. I understand the issue and difference; I just didn't realize 2.6 was closed -- I didn't really mean that this should be fixed in anything other than the current or even next release of anything. On Dec 24, 2010, at 3:36 PM, Terry J. Reedy wrote: Terry J. Reedy tjre...@udel.edu added the comment: Mitchell: 2.6 is closed to revision except for security issues -- nosy: +terry.reedy resolution: wont fix - versions: +Python 3.2 -Python 2.6 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10733 ___ -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10733 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2636] Regexp 2.7 (modifications to current re 2.2.2)
R. David Murray rdmur...@bitdance.com added the comment: I suspect it would help if there are more changes, though. I believe that to push to launchpad you have to upload an ssh key. Not sure why you'd get no such account, though. Barry would probably know :) -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue2636 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2636] Regexp 2.7 (modifications to current re 2.2.2)
Matthew Barnett pyt...@mrabarnett.plus.com added the comment: It does have an SSH key. It's probably something simple that I'm missing. I think that the only change I'm likely to make is to a support script I use; it currently uses hard-coded paths, etc, to do its magic. :-) -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue2636 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue5258] addpackage in site.py fails hard on badly formed .pth files
R. David Murray rdmur...@bitdance.com added the comment: Yes, I think it is a good idea for site.py to issue error messages and continue on when it is processing files that don't come from the python distribution itself (such as pth files). However, I think just printing the error message is not going to provide enough info. For example the error in this issue would produce something like: TypeError: embedded NUL character Which wouldn't be much of a clue as to what went wrong. Likewise the case of a pth file containing a like this: import foo)bar This would result in an error message like this: SyntaxError: invalid syntax This seems fine at first glance, but what if the pth file is: import foo and foo.py is: foo)bar We get the *same* error message, but the pth file itself is syntactically correct. So, I think it is better to print the traceback, even if it results in extra info (lines from the addpackage routine itself). Attached is a patch that takes this approach. I locate this code in addpackage itself so that I can get the line number from the pth file for the error message, further localizing it. And I wrap all of the code that I think could throw errors due to bad pth files, but only that code. Note that both of these patches also address issue 10642, so I'm going to make this a superseder for that issue. If you like this approach, Georg, then we just need unit tests :) -- stage: - patch review Added file: http://bugs.python.org/file20159/site_pth_exceptions.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue5258 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10642] Improve the error message of addpackage() (site.py) for defective .pth file
R. David Murray rdmur...@bitdance.com added the comment: Georg posted a patch to issue 5258 that would fix this. I've posted a counter proposal that would give more info. We're proposing to simply write to stderr and then continue. With either patch this issue would be fixed, so I'm making that issue a superseder for this one. -- resolution: - duplicate status: open - closed superseder: - addpackage in site.py fails hard on badly formed .pth files ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10642 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue5258] addpackage in site.py fails hard on badly formed .pth files
Changes by R. David Murray rdmur...@bitdance.com: -- nosy: +Arfrever, dwr2, eric.araujo, haypo, tarek ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue5258 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10771] descriptor protocol documentation has two different definitions of owner class
New submission from Devin Jeanpierre jeanpierr...@gmail.com: In trunk/Doc/reference/datamodel.rst , under _Implementing Descriptors_, the documentation states: `The following methods only apply when an instance of the class containing the method (a so-called *descriptor* class) appears in the class dictionary of another new-style class, known as the *owner* class. [...]` Immediately below, in the documentation for __get__, it says, `*owner* is always the owner class [...]`. These two uses of the owner class are incompatible, because there is only one class which matches the first use: the class where the descriptor was initially assigned to a class attribute; however, for the second use, any descendant class may be called the owner class. This is demonstrated in the attached doctest file. It is kind of hard to create a better definition for owner as used in `__get__`, though. It can't be said to be the class with the descriptor in its class dict, because it can be present in the class dict of some class in the MRO of the owner. It can't be said to be an attribute, because it has to be in a class dict of an ancestor node. It might be possible to change the definition to call the owner class something like, the class from which the descriptor was invoked, and if that isn't clear enough, provide examples (TypeDescriptor from the attached doctest file might work as an example); however, this would involve reworking the structure of the paragraph substantially. I personally would prefer this option. The paragraph is already badly structured; for example, it defines two terms in a single and rather complex sentence, and should probably be split up into a list of definitions rather than an explanatory jumble paragraph. In addition, this paragraph is the only place in the documentation where this idea of the owner class is used in this way. In the descriptions of the descriptor protocol methods below it, the owner class always refers to the class from which the attribute was accessed, or the type from which an instance had the attribute accessed. Alternatively, it could be simpler to replace all references below from the owner class to any class with the owner class in the MRO. -- assignee: d...@python components: Documentation files: descriptor.py.doctest messages: 124630 nosy: Devin Jeanpierre, d...@python priority: normal severity: normal status: open title: descriptor protocol documentation has two different definitions of owner class versions: Python 2.7 Added file: http://bugs.python.org/file20160/descriptor.py.doctest ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10771 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10576] Add a progress callback to gcmodule
Kristján Valur Jónsson krist...@ccpgames.com added the comment: Well, the idea is good and it did cross my mind. Particularly it could be useful for performance sensitive applications. However it complicates things. 1) If a GC is rejected, when do we make the next attempt? 2) If a callback cancels GC, then what about the other callbacks that have already been called? They would need to get some canceled call. But this is ok, I suppose. Since we have already passed the beta 2, I'll see if I can come up with a simple change, particularly if we don't descend into some infinite loop wrt. 1) above. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10576 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
