Mailman 3 May 2001 - Python-Dev

"data".decode(encoding) ?!
by M.-A. Lemburg May 7, 2001

May 7, 2001

We already have "data".encode(encoding) which encodes the string data by passing it through the encoder of the given encoding. Wouldn't it be worthwhile to add direct access to codec decoders through string methods as well ? (Note that this addition only makes sense for string objects, since Unicode cannot be decoded.) Also, would there be any objections adding some more standard codecs to the system ? I'm thinking of wrapping the binascii module APIs in form of codecs... -- Marc-Andre … [View More]

4 10

Moving MacPython to sourceforge
by Martin von Loewis May 7, 2001

May 7, 2001

> There's two ways I can go about this: start a new MacPython project > or merge the MacPython stuff into the main Python CVS repository. There is actually a third option: Use the Python SF project, but create a new module in the Python CVS repository (so no merging would be done). I don't know how much code this is. I'd favour merging the Mac code into the core distribution. If there are loads of Mac-specific modules that not every MacPython user needs, it might be advisable to create … [View More]

2 1

Re: [Python-Dev] Added a machine-dependent file to the core
by Jack Jansen May 7, 2001

May 7, 2001

> Jack Jansen wrote: > > To my surprise I noticed that the whole configure/Makefile.pre.in/setup setup > > of Python does not allow for an easy addition of a platform-dependent > > sourcefile to the core interpreter (or am I missing something?). > [...] > > > > Is it OK if I add a MACHDEP_OBJS to PYTHON_OBJS? > > How would this work? Would MACHDEP_OBJS be set by an autoconf > subsitution? Yes, that's what I had in mind (haven't written the code … [View More]

2 1

Added a machine-dependent file to the core
by Jack Jansen May 7, 2001

May 7, 2001

To my surprise I noticed that the whole configure/Makefile.pre.in/setup setup of Python does not allow for an easy addition of a platform-dependent sourcefile to the core interpreter (or am I missing something?). This is a bit of functionality I need to port the various Mac modules to MacOSX-python. The platform depende sourcefile has various glue routines for turning MacOS error codes into exceptions and that sort of stuff. Is it OK if I add a MACHDEP_OBJS to PYTHON_OBJS? -- Jack Jansen … [View More]

2 1

Need a search path for modules in setup.py
by Jack Jansen May 7, 2001

May 7, 2001

(Don't worry, this is the last in my flurry of OSX related messages:-) Life would be a lot simpler for me if setup.py (the one for the main extension modules) would have a search path for module sourcefiles. As Mac modules currently live in Python/Mac/Modules (as opposed to Python/Modules) not having a search path measn I get ugly "../Mac/Modules/foomodule.c" constructs. I have the code for setup.py ready, is it OK if I check it in? -- Jack Jansen | ++++ stop the execution of … [View More]

1 0

multiple inheritance -- what I meant
by Paul F. Dubois May 5, 2001

May 5, 2001

When I suggested a modification to the inheritance clause, class X (Y rename a as b, c as d, Z rename foo as bar): someone suggested this was the same as class X (Y, Z): b = Y.a d = Y.c bar = Z.foo I meant two things by my suggestion: 1. I meant that Y.a would never be found when searching for X.a. In particular, if Z.a exists, and a is not explicity defined in X, X.a is Z.a. 2. More philosophically, rather than being a consequence of the language like the second method is, … [View More]

1 0

PySequence_Contains
by Guido van Rossum May 5, 2001

May 5, 2001

In a checkin message, Tim wrote: > The full story for instance objects is pretty much unexplainable, because > instance_contains() tries its own flavor of iteration-based containment > testing first, and PySequence_Contains doesn't get a chance at it unless > instance_contains() blows up. A consequence is that > some_complex_number in some_instance > dies with a TypeError unless some_instance.__class__ defines __iter__ but > does not define __getitem__. This kind of … [View More]

2 5

"".tokenize() ?
by M.-A. Lemburg May 5, 2001

May 5, 2001

Gustavo Niemeyer submitted a patch which adds a tokenize like method to strings and Unicode: "one, two and three".tokenize([",", "and"]) -> ["one", " two ", "three"] I like this method -- should I review the code and then check it in ? PS: Haven't gotten any response regarding the .decode() method yet... should I take this as "no objections" ? -- Marc-Andre Lemburg ______________________________________________________________________ Company & Consulting: … [View More]

5 8

::
by Paul Prescod May 4, 2001

May 4, 2001

I'll throw out a partially formed thought in case it is useful to anybody. "::" might be useful to solve another problem I've been struggling with: how to have multiple package distributions share a namespace (xml::dom::minidom, xml::dom::4dom, xml::dom::corbadom). "::" might mean, in general, that you are walking through abstract, potentially merged namespaces and not through concrete dictionary implementations. I think that Python's using the same syntax for package namespaces and … [View More]

2 1

Change to PyIter_Next()?
by Tim Peters May 4, 2001

May 4, 2001

In spare moments, I've been plugging away at making various functions work nice with iterators (map, min, max, etc). Over and over this requires writing code of the form: op2 = PyIter_Next(it); if (op2 == NULL) { /* StopIteration is *implied* by a NULL return from * PyIter_Next() if PyErr_Occurred() is false. */ if (PyErr_Occurred()) { if (PyErr_ExceptionMatches(PyExc_StopIteration)) PyErr_Clear(); else goto Fail; } break; } This is wordy, obscure, and in my … [View More]

2 2