[issue1009] Implementation of PEP 3101, Advanced String Formatting

Eric V. Smith added the comment: Closed, code was checked in revision 57444. -- versions: +Python 3.0 -Python 2.6 __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1009 __

[issue1009] Implementation of PEP 3101, Advanced String Formatting

Eric V. Smith added the comment: I tried to close it, without success. Possible tracker issue, I'll investigate. It should be closed! __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1009 __

[issue1764407] The -m switch does not use the builtin __main__ module

Nick Coghlan added the comment: Fixed committed to SVN as r57461 -- resolution: - fixed status: open - closed _ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1764407 _

[issue1574217] isinstance swallows exceptions

Changes by Brian Harring : -- versions: +Python 2.5 _ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1574217 _

[issue1018] server-side ssl support

Guido van Rossum added the comment: Committed revision 57464. -- resolution: - accepted status: open - closed __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1018 __

[issue1020] pydoc doesn't work on pyexpat

New submission from Neal Norwitz: help(pyexpat) causes an exception: Traceback (most recent call last): File stdin, line 1, in module File /home/neal/python/dev/py3k/Lib/site.py, line 350, in __call__ return pydoc.help(*args, **kwds) File /home/neal/python/dev/py3k/Lib/pydoc.py, line

[issue1021] logging.basicConfig does not allow to set NOTSET level

Changes by viper: -- components: Library (Lib) severity: minor status: open title: logging.basicConfig does not allow to set NOTSET level versions: Python 2.5 __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1021

[issue1022] use bytes for code objects

New submission from Neal Norwitz: This patch has a hack to read in marshaled code objects. Bytes can't be marshaled currently (they are stored as strings). So when reading a marshaled code object, the hack converts them to bytes. All tests except test_modulefinder pass. The issue is that

[issue1023] [PATCH] Unicode fixes in floatobject and moduleobject

New submission from Ero Carrera: Removed calls to _PyUnicode_AsDefaultEncodedString and replaced them wit PyUnicode_AsString. Also removed calls to PyString_* and replaced them by the equivalent PyUnicode_* -- files: floatobject_moduleobject_pystring.patch messages: 55291 nosy:

[issue1018] server-side ssl support

Changes by Bill Janssen: -- nosy: +janssen __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1018 __ ___ Python-bugs-list mailing list Unsubscribe:

[issue1467929] %-formatting and dicts

Sean Reifschneider added the comment: I'm attaching a new version of this which includes AMK's string patch ported over to unicode. Any objections to my committing this to the trunk? Should it also go in for the next 2.5 release? -- nosy: +jafo _

[issue1024] documentation for new SSL module

New submission from Bill Janssen: Here's a documentation patch for the SSL code that was checked in yesterday. It removes discussion of SSL from the socket documentation, makes a change to the urllib2 doc's discussion of how to test for SSL support, and adds documentation of the SSL module

[issue1024] documentation for new SSL module

Bill Janssen added the comment: Sorry, long day: ...and its features... __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1024 __ ___ Python-bugs-list mailing list Unsubscribe:

[issue1024] documentation for new SSL module

Changes by Bill Janssen: -- components: +Documentation __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1024 __ ___ Python-bugs-list mailing list Unsubscribe:

[issue1114345] Add SSL certificate validation

Bill Janssen added the comment: I believe this is now fixed with patch 1018. -- nosy: +janssen _ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1114345 _ ___

[issue1027394] socket.ssl should explain that it is a 2/3 connection

Bill Janssen added the comment: Patch 1024 is new documentation which addresses this. Is is sufficient? -- nosy: +janssen _ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1027394 _

[issue889813] making the version of SSL configurable when creating sockets

Bill Janssen added the comment: I believe issue 1018 now fixes this. -- nosy: +janssen Tracker [EMAIL PROTECTED] http://bugs.python.org/issue889813 ___ Python-bugs-list

[issue1583946] SSL issuer and server names cannot be parsed

Bill Janssen added the comment: I believe issue 1018 addressed this, and that it can be closed. Though socket.ssl, and its methods server and issuer, should be deprecated. -- nosy: +janssen _ Tracker [EMAIL PROTECTED]

[issue1217246] proposed patch for tls wrapped ssl support added to smtplib

Bill Janssen added the comment: This probably needs to be re-written with the new SSL support in 2.6. See issue 1024. -- nosy: +janssen _ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1217246 _

[issue783188] support for server side transactions in _ssl

Bill Janssen added the comment: I believe issue 1018 renders this one moot. Though more examples in Demo is still a good idea. I'll contribute a threaded server example for that. -- nosy: +janssen Tracker [EMAIL PROTECTED]

[issue1706815] socket.error exceptions not subclass of StandardError

Bill Janssen added the comment: It's not clear to me that having the SSL errors inherit from socket.error is a good idea. Many of them have nothing to do with the socket, but are errors in choice of cipher, certificate validation, etc. -- nosy: +janssen

[issue1583946] SSL issuer and server names cannot be parsed

Changes by Gregory P. Smith: -- nosy: -greg _ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1583946 _ ___ Python-bugs-list mailing list Unsubscribe:

[issue1706815] socket.error exceptions not subclass of StandardError

Gregory P. Smith added the comment: Does the existing python SSL implementation allow it to be used over something other than a socket? If so then yes that makes sense, but otherwise its best to leave its inheritance from socket.error so that code that works when handed a regular socket can

[issue1025] tracebacks from list comps (probably other comps) don't show full stack

New submission from Neal Norwitz: A traceback that occurs within a list comprehension (and probably all comprehensions) only shows the stack from the comprehension, not the entire scope: Traceback (most recent call last): File Lib/test/test_multibytecodec_support.py, line 35, in