[issue1711603] syslog syscall support for SysLogLogger

Max Arnold added the comment: Can I vote for this issue? Many systems with syslog aren't configured to listen on UDP socket and thus out of the box SysLogHandler does not work. -- nosy: +LwarX ___ Python tracker

[issue1711603] syslog syscall support for SysLogLogger

Vinay Sajip added the comment: As the docstring and documentation says, you can use SysLogHandler("/dev/log") or similar to connect to a local syslog using Unix domain sockets rather than UDP. Doesn't this work for you? -- ___ Python tracker

[issue5590] pyexpat defines global symbol template_string

Matthias Klose added the comment: fixed in rev 73503 -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___ Python

[issue4949] Constness in PyErr_NewException

Changes by Andreas Kloeckner : -- versions: +Python 2.7 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://m

[issue6322] Pdb breakpoints don't work on lines without bytecode

New submission from Andreas Kloeckner : Take this program: 8< --- print "START" a = [ 1 for i in range(10)] 8< --- as "a.py", run "python -m pdb a.py", say "b 3" to set a breakpoint on line

[issue1711603] syslog syscall support for SysLogLogger

Max Arnold added the comment: Is it safe to use single handler instance in multiple loggers or single stream in multiple handlers? -- ___ Python tracker ___ __

[issue6323] Py3.1 pdb doesn't deal well with syntax errors

New submission from Andreas Kloeckner : Steps to reprdocue: 1) Debug a program with a syntax error in pdb. 2) Get the SyntaxError traceback. 3) Hit "q" to quit. 4) Another SyntaxError traceback, and you're back at the Pdb prompt. -- components: Library (Lib) messages: 89599 nosy: induc

[issue1711603] syslog syscall support for SysLogLogger

Vinay Sajip added the comment: Why would you want to use a single handler instance against multiple loggers? It's safe to do so, but you could get duplicated messages appearing. I presume you have reviewed the documentation and are aware that loggers are organised in a hierarchy and that in the

[issue1711603] syslog syscall support for SysLogLogger

Max Arnold added the comment: Sorry, I've read your first reply too fast and incorrectly interpreted it as recommendation to use stream handler with /dev/log. Anyway, thank you for clarification. -- ___ Python tracker

[issue1100942] Add datetime.time.strptime and datetime.date.strptime

Changes by Tuk Bredsdorff : -- nosy: +tiktuk ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyth

[issue6070] Python 2.6 makes .pyc/.pyo bytecode files executable

Oleg Broytmann added the comment: import_patch2.patch doesn't work for me. I patched and compiled Python 2.6.2 and without installing it ran ./python -c "import test" in the build directory. It copied executable bits from test.py to test.pyc. -- ___

[issue6070] Python 2.6 makes .pyc/.pyo bytecode files executable

Marco added the comment: hmm.. the problem is that Windows doesn't support well permissions as all the other POSIX compliant OSs ... I've searched for a solution on the web, and I've found a complete answer on: http://stackoverflow.com/questions/592448/c-how-to-set-file-permissions-cross-platfor

[issue6070] Python 2.6 makes .pyc/.pyo bytecode files executable

Oleg Broytmann added the comment: I am not on Windows. I am on Linux. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsu

[issue5910] kqueue for more than one event is broken.

Amaury Forgeot d'Arc added the comment: The patch looks good, but I cannot test it. -- assignee: -> christian.heimes nosy: +amaury.forgeotdarc ___ Python tracker ___ ___

[issue6285] Silent abort on XP help document display

Amaury Forgeot d'Arc added the comment: I reproduce the same problem: In IDLE, add a new entry in "Options/Configure/General/Additional Help Sources", and browse to the C:\Python31\Docs\Python31*.chm file. This new entry appears in the "Help" menu. Now, if you un-install this version and insta

[issue6324] "in" expression falls back to __iter__ before __getitem__

New submission from Anthony Foglia : I was debugging a class where I defined __getitem__ and __iter__, but not __contains__. The documentation describing this case (at the end of section 5.9) is old and hasn't been updated for the iterator protocol. It should read something like: "For user-d

[issue4490] xml/sax/expatreader.py raises AttributeError when run

Amaury Forgeot d'Arc added the comment: These functions are already tested, but I think that this kind of code also serves to show a basic usage of the module. Fixed with r73509. -- nosy: +amaury.forgeotdarc resolution: -> fixed status: open -> closed

[issue6323] Py3.1 pdb doesn't deal well with syntax errors

Amaury Forgeot d'Arc added the comment: I tried different combinations, and could not reproduce it (for example, the debugged function imports a bad module, or eval() a bad expression) How did you generate the SyntaxError? -- nosy: +amaury.forgeotdarc stage: -> test needed __

[issue6323] Py3.1 pdb doesn't deal well with syntax errors

nlopes added the comment: I can reproduce it in my OpenBSD 4.5 box (only one I tried). This simple code: print(3 seems to break the pdb flow in python 3.1 the way Andreas described it. When I tried in 2.7, this is what I get: -bash-3.2$ ./python -m pdb test.py SyntaxError: ('invalid syntax', (

[issue1424152] urllib/urllib2: HTTPS over (Squid) Proxy fails

Andrew Trick added the comment: With this patch, I continued to get the following error SSL23_GET_SERVER_HELLO Until my coworker finally found a fix posted by Philippe Biondi: +++ b/mercurial/keepalive.py @@ -237,6 +237,8 @@ else: # no (working) free connections

[issue6324] "in" expression falls back to __iter__ before __getitem__

Changes by Raymond Hettinger : -- assignee: georg.brandl -> rhettinger nosy: +rhettinger ___ Python tracker ___ ___ Python-bugs-list ma

[issue6290] cPickle can misread data type

Alex James added the comment: I have now pinpointed the error to a list of infinities (see attached). When using pickle.py to read the cPickle'd data we get a different, and more, informative error: ValueError: invalid literal for float(): 1.#INF -- Added file: http://bugs.python.org/fi

[issue1298813] sysmodule.c: realpath() is unsafe

Changes by jan matejek : -- nosy: +matejcik ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pytho

[issue6323] Py3.1 pdb doesn't deal well with syntax errors

Amaury Forgeot d'Arc added the comment: Thanks for the test case. It appears that 2.7 actually calls exec("execfile(filename)"), when 3.1 directly calls exec(file_content). The indirection seems necessary: the SyntaxError is detected by the pdb trace function; but this function has to run some

[issue6323] Py3.1 pdb doesn't deal well with syntax errors

nlopes added the comment: That fixes it. It seems to be introduced when committing a fix for issue #1038. -bash-3.2$ svn diff -r 58126:58127 Lib/pdb.py Index: Lib/pdb.py === --- Lib/pdb.py (revision 58126) +++ Lib/pdb.py (revisio

[issue6070] Python 2.6 makes .pyc/.pyo bytecode files executable

R. David Murray added the comment: The patch did not apply for me. I modified the code by hand based on the patch file, and on Gentoo linux it worked for me. Patch that applies cleanly to trunk attached. -- nosy: +r.david.murray priority: -> low stage: -> test needed versions: +Pyth

[issue6323] Py3.1 pdb doesn't deal well with syntax errors

Amaury Forgeot d'Arc added the comment: Good point. So in the end, we just replaced exec('%s')# wrong when the text is "x='a'" with exec(%r) -- ___ Python tracker ___

[issue1424152] urllib/urllib2: HTTPS over (Squid) Proxy fails

Senthil added the comment: AndrewTrick: I am assuming your last comment is more relevant to mercurial's use of the set_tunnel, the facility provided by the patch, that is solving the issue for you. You had earlier pointed out mercurial's dependency upon this issue too. The fix as such stands go

[issue5230] pydoc reports misleading failure if target module raises an ImportError

R. David Murray added the comment: OK, I finally had time to come back to this, and figured out what I think is a final fix. It passes all the tests we've come up with, at least. Let me know if you see any problems with it, and if not I'll apply it. -- assignee: -> r.david.murray ver

[issue5230] pydoc reports misleading failure if target module raises an ImportError

Changes by R. David Murray : Removed file: http://bugs.python.org/file14205/issue5230.patch ___ Python tracker ___ ___ Python-bugs-list mailing

[issue6290] cPickle can misread data type

Alexandre Vassalotti added the comment: Thanks for the test case. I will take a look. -- assignee: georg.brandl -> alexandre.vassalotti components: +Library (Lib) -Documentation, Extension Modules, Windows ___ Python tracker

[issue6290] cPickle can misread data type

Alexandre Vassalotti added the comment: Could you give me the output of this? import cPickle print repr(cPickle.dumps([float('+inf'), float('-inf'), float('nan')])) print [float('+inf'), float('-inf'), float('nan')] By the way, are you sure this bug occurs on Python 2.6? Python 2.6 uses

[issue1424152] urllib/urllib2: HTTPS over (Squid) Proxy fails

Andrew Trick added the comment: I should have pointed out that my secondary problem was a mercurial dependency on the urllib patch. I just wanted Mercurial users to get a complete fix. I figure they will be looking for a fix in the python bug report, and need to be told the fix won't work for th

[issue6325] robotparser doesn't handle URL's with query strings

New submission from Brian Slesinsky : If a robots.txt file contains a rule of the form: Disallow: /some/path?name=value This pattern will never match a URL passed to can_fetch(), as far as I can tell. It's arguable whether this is a bug. The 1994 robots.txt protocol is silent on whether to t

[issue6233] ElementTree (py3k) doesn't properly encode characters that can't be represented in the specified encoding

Jerry Chen added the comment: The attached patch includes Neil's original additions to test_xml_etree.py. I also noticed that _encode_entity wasn't being called in ElementTree in py3k, with the important bit being the nested function escape_entities(), in conjunction with _escape and _escape_m