Re: [Python-Dev] PEP 340: Non-looping version (aka PEP 310 redux)

directly. Thats not true of the block generator API. -- Toby Dickenson ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail

Re: [Python-Dev] PEP 344: Exception Chaining and Embedded Tracebacks

. Should that be if the exception instance does not already have a __context__ attribute or the value of that attribute is None -- Toby Dickenson ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev

Re: [Python-Dev] PEP 348 (exception reorg) revised again

module?). It makes sense to express the classification of exceptions that are intended to terminate the interpreter, but we dont need to express that classification as inheritence. -- Toby Dickenson ___ Python-Dev mailing list Python-Dev@python.org http

Re: [Python-Dev] The path module PEP

be reasonable to expect to use bar=='/etc/*' -- Toby Dickenson ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Re: [Python-Dev] Syntax suggestion for imports

Raymond Hettinger wrote: [Jeroen Ruigrok van der Werven] On the Trac project using your grep gives me 203 lines, if we take ~2 lines for and after in consideration, it still means 203/5 ~= 40 occurences. Thanks. I'm more curious about the content of those lines. Does the proposed syntax

Re: [Python-Dev] Warn about mktemp once again?

Tristan Seligmann wrote: The correct way to do this is to create a temporary directory, and then generate a filename underneath that directory to use. There is a platform difference here. On unix mktemp will usually provide a file name in a world-writeable directory (/tmp/) which is wide open