But that's what beta releases are for, right? I have to say I always thought Guido was a bit conservative. In the mean time, I thank everybody who worked very hard to make this release a success. I don't see anything confusing about having unicode-escape be the appropriate escape used for repr. I prefer the former solution and unless someone screams I will check that in in a few hours. Just adding IndentationError for -tt isn't hard, I have a preliminary patch for that now.
I could allow them to tell me what encoding to use, but surely they would rather do that in a Python-wide fashion. What about the Mail-Followup-To header? This line of code has the same number of spaces at the start as the one before, but the last line was expected to start a block e. Would one of the admins using Netscape please check that page for sane display? Cheers, -g -- Greg Stein, From mhammond skippinet. The following exceptions are used as warning categories; see the Warning Categories documentation for more details. Once that comes out of beta, I would consider it a core-library candidate. As soon as you have two people together, there is a large chance you'll disagree about tab size.
I would also like to adjust the regrtest. The possession of arms is the distinction between a freeman and a slave. If we want to use a hard-coded lossless encoding, we should do so in repr. The summary seems pretty good to me. Loewis writes: Now that the file copyrights are changed, I expect this message to change as well. That can be helpful for some newsreaders e.
Python cannot decide where it goes. Cheers, -g -- Greg Stein, From Vladimir. This module never needs to be imported explicitly: the exceptions are provided in the built-in namespace as well as the exceptions module. BeOpen PythonLabs Team Member From skip mojam. I did successfully update one of my patches but now that feature no longer seems to work. But I don't understand why you want an integer. The pipermail archives on python.
In-Reply-To: ; from esr thyrsus. If naive Python programmers cannot generate usable parsers then it may not be appropriate for the standard library. Can you give this a try? Only through the careful eye of some -checkins watchers has that fact turned up. But that's what beta releases are for, right? If those people weren't watching, we'd be lost. If anyone's game, take a look at Thanks. If the default encoding is lossless then repr could use it.
Simply because auto-conversion should use one single encoding throughout the code. Cheers, -g -- Greg Stein, From gstein lyra. Did Barry ever track down the mysterious crashes he was seeing from running the test suite? Raymond No kingdom can be secured otherwise than by arming the people. I've prefer not to have several lines of spammage hit my screen whenever I invoked Python. A good way to test drive this, is running Python with -U option.
Or at least one which defines all non-cased letters. One potential solution for Mailman might be to lie about the To: address. Paul Prescod writes: +1 That would be great for newbies! After all, the checkin is already labeled as yours. This line of code has more spaces at the start than the one before, but the one before is not the start of a subblock e. This system uses a wizard to help with the installation of the operating system. It looks ahead to see if it really is a quantifier or not.
I'd certainly expect that a minidom Node can be printed always, no matter what the default encoding is. Errors you can get are: Unexpected indent. Yes, I can ssh to my SouurceForge account with no problems. Greg -- Greg Ward - software developer gward mems-exchange. And I'm sure you'll find the way to do it. Rather than having us fix a dozen modules with problems like this, we should fix repr once and for all.