[Python-Dev] Looking for the email addresses of some committers

If someone can email me the addresses for the following committers, I would appreciate it: * Greg Stein * Jackilyn Hoxworth * Jeff Senn * John Benediktsson * Mateusz Rukowicz * Richard Emslie * Roy Smith And if any of the above people no longer want commit privileges or were only given them tempo

Re: [Python-Dev] Memory Error while reading large file

Martin v. Löwis wrote: (maybe the use of the question mark is more typical in German than in English; my stomach turns around when I read a question that ends with a full stop) No, it's required in English, too. -- Greg ___ Python-Dev mailing lis

Re: [Python-Dev] Memory Error while reading large file

On Thu, Jul 31, 2008 at 2:38 PM, Scott Dial <[EMAIL PROTECTED]> wrote: > Martin v. Löwis wrote: >> >> (maybe the use of the question mark is more typical in German >> than in English; my stomach turns around when I read a question >> that ends with a full stop) > > There is no loss in translation h

Re: [Python-Dev] Memory Error while reading large file

Martin v. Löwis wrote: (maybe the use of the question mark is more typical in German than in English; my stomach turns around when I read a question that ends with a full stop) There is no loss in translation here. Proper English requires the use of a question mark just the same as German,

Re: [Python-Dev] Memory Error while reading large file

> If you have an actual question I'd like to stress this point as well. Any good posting one wants an answer to must include a question, and that question must be explicitly phrased, and terminated with a question mark. (maybe the use of the question mark is more typical in German than in Engl

Re: [Python-Dev] critical issues for 2.6 and 3.0

> I've never been through a Python release before, but I find these > statistics rather worrying if we want to make the October release > date. I don't worry. Every Python release had bugs, and there will be 2.6.1 and 3.0.1 releases. The only sure way to resolve bugs is to revert features. If a c

Re: [Python-Dev] Matrix product

Nick Coghlan write: > Sebastien Loisel wrote: >> Dear Raymond, >> >> Thank you for your email. >> >>> I think much of this thread is a repeat of conversations >>> that were held for PEP 225: >>> http://www.python.org/dev/peps/pep-0225/ >>> >>> That PEP is marked as deferred. Maybe it's time to >>

Re: [Python-Dev] urllib.quote and unquote - Unicode issues

> so you can use quote_from_bytes on strings? Yes, currently. > I assumed Guido meant it was okay to have quote accept string/byte input and > have a function that was redundant but limited in what it accepted (i.e. > quote_from_bytes accepts only bytes) > > I suppose your implementation doesn'

Re: [Python-Dev] urllib.quote and unquote - Unicode issues

> > > quote_from_bytes = quote >> > > So either name can be used on either input type, with the idea being that > you should use quote on a str, and quote_from_bytes on a bytes. Is this a > good idea or should it be rewritten so each function permits only one input > type? > > so you can use quote_

Re: [Python-Dev] Matrix product

Sebastien Loisel wrote: Dear Raymond, Thank you for your email. I think much of this thread is a repeat of conversations that were held for PEP 225: http://www.python.org/dev/peps/pep-0225/ That PEP is marked as deferred. Maybe it's time to bring it back to life. This is a much better PEP

Re: [Python-Dev] urllib.quote and unquote - Unicode issues

Bill wrote: I'm not sure that's sufficient review, though I agree it's necessary. > The major consumers of quote/unquote are not in the Python standard > library. I figured that Python 3.0 is designed to fix things, with the breaking third-party code being an acceptable side-effect of that. So t

Re: [Python-Dev] urllib.quote and unquote - Unicode issues

Alright, I've uploaded the new patch which adds the two requested bytes-oriented functions, as well as accompanying docs and tests. http://bugs.python.org/issue3300 http://bugs.python.org/file11009/parse.py.patch6 I'd rather have two pairs of functions, so that those who want to give > the readers

Re: [Python-Dev] urllib.quote and unquote - Unicode issues

Bill Janssen writes: > > A quoting function that accepts bytes *must* have an encoding > > argument. > > Huh? What would it use it for? Ah, you're right. I was thinking in terms of an URI builder, where the quoter would do any required conversion (eg, if the bytes represented a string in J

Re: [Python-Dev] urllib.quote and unquote - Unicode issues

Also see . Bill ___ 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] urllib.quote and unquote - Unicode issues

> Of course, it's un-Pythonic to enforce pedantry, and we pedants can > use a string->string encoder correctly. Sure. All I was asking was that we not break the existing usage of the standard library "unquote" by producing a string by *assuming* a UTF-8 encoded string is what's in those percent-e

Re: [Python-Dev] urllib.quote and unquote - Unicode issues

> Guido says: > > > Actually, we'd need to look at the various other APIs in Py3k before we can > > decide whether these should be considered taking or returning bytes or text. > > It looks like all other APIs in the Py3k version of urllib treat URLs as > > text. > > > Yes, as I said in the bug

Re: [Python-Dev] Memory Error while reading large file

On Thu, 31 Jul 2008 03:01:42 pm Sumant Gupta wrote: > Hi > > I have a problem reading very large text file. > When I call the len function to get the total lines in python file.i > get memory error . I am reading the list of files in a loop ,2 files > are read properly but when the third file is re