Mailman 3 December 2002 - Python-Dev

RE: how to kill process on Windows started with os.spawn?
by Skip Montanaro Dec. 3, 2002

Dec. 3, 2002

Regarding how to kill a process on Windows which was started with os.spawn*, on the Spambayes list I asked: >> How would I kill that process on Windows, Mark Hammond replied: This worked for me just then: >>> os.spawnl(os.P_NOWAIT, "f:\\windows\\notepad.exe") 548 >>> import win32api >>> win32api.TerminateProcess(548,0) Tim also replied: Tim> For 2.3, I implemented something or other for the Python core; Tim> probably … [View More]

7 12

Re: [Python-Dev] Getting python-bz2 into 2.3
by Bob Kline Dec. 3, 2002

Dec. 3, 2002

Earlier this month, Tim P. wrote: > Semi-unfortunately, the author of that [bzip2] has > > no idea if it actually works on 95/98/ME/NT/XP > > and in the docs for "3.8 Making a Windows DLL" > > I haven't tried any of this stuff myself, but it all looks > plausible. > > That means it will require some real work to build and test this > stuff on 6 flavors of Windows. Not a showstopper, but does raise > the bar for getting into the PLabs Windows … [View More]

4 9

ssl for Windows
by Mark Hammond Dec. 3, 2002

Dec. 3, 2002

I would like to check in a patch for http://www.python.org/sf/576711, which adds the _ssl module to Windows builds. The only slightly controversial thing is how the build process operates. I have quoted the relevant part of PCbuild/readme.txt below. test_socket_ssl passes once this is built, and at least 2 other people have reported build success. Are there any objections to the scheme? Should I check it in? Mark. _ssl Python wrapper for the secure sockets library. Get the … [View More]

2 1

RE: [Python-checkins] python/nondist/sandbox/datetime obj_delta.c,1.14,1.15 test_both.py,1.15,1.16
by Jeremy Hylton Dec. 2, 2002

Dec. 2, 2002

>>>>> "TP" == Tim Peters <tim.one(a)comcast.net> writes: TP> I'd rather find a way to avoid __reduce__ entirely, though! Me, too! TP> The Python implementation of these things didn't need it, and in TP> the date and datetime cases it's creating bigger pickles than it TP> should -- __getstate__ and __setstate__ already did all that was TP> necessary, and no more than that. Supplying an argument tuple TP> for __reduce__'s benefit loses either … [View More]

1 0

Re: [Python-checkins] python/nondist/sandbox/datetime obj_delta.c,1.14,1.15 test_both.py,1.15,1.16
by Michael Hudson Dec. 2, 2002

Dec. 2, 2002

tim_one(a)users.sourceforge.net writes: > + /* XXX A further broken attempt to get pickling to work. > + * XXX This avoids the problem above, but dies instead with > + * XXX PicklingError: Can't pickle <type 'timedelta'>: it's not > + * XXX found as __builtin__.tmedelta You need to arrange for a module name to appear in timedelta's tp_name: Index: obj_delta.c =================================================================== RCS file: /cvsroot/python/python/… [View More]

2 1

Sleepycat Berkeley DB on OSX
by Guido van Rossum Dec. 2, 2002

Dec. 2, 2002

When running test_bsddb3 on Mac OSX, using BSDDB 4.0.14, I get tracebacks like these: Exception in thread writer 0: Traceback (most recent call last): File "/Users/guido/python/src/Lib/threading.py", line 416, in __bootstrap self.run() File "/Users/guido/python/src/Lib/threading.py", line 404, in run apply(self.__target, self.__args, self.__kwargs) File "/Users/guido/python/src/Lib/bsddb/test/test_thread.py", line 115, in writerThread dbutils.DeadlockWrap(d.put, key, self.… [View More]

2 1

PyArg_Parse (was: int/long FutureWarning)
by Jack Jansen Dec. 2, 2002

Dec. 2, 2002

Martin: > Jack Jansen <Jack.Jansen(a)oratrix.com> writes: > >> How about taking a completely different angle on this matter, and >> looking at PyArg_Parse itself? If we can keep PyArg_Parse 100% >> backward compatible (which would mean that its "i" format would take >> any IntObject or LongObject between -1e31 and 1e32-1) and introduce a >> new (preferred) way to parse arguments that not only does the right >> thing by being expressive enough to … [View More]make a difference between >> "currency integers" and "bitmap integers", but also cleans up the >> incredible amount of cruft that PyArg_Parse has accumulated over the >> years? > > I had a similar idea, so I'd encourage you to spell out your proposal > in more detail, or even in an implementation. > My idea was to provide a ParseTuple wrapper, [...] > Those of you needing to support older Python releases could > > #define PyArg_ParseTupleLenient PyArg_ParseTuple > > in your distribution, or provide other appropriate wrappers. Unfortunately this wouldn't work if the distributions are binary distributions. But, aside from that, I think I would want to go much further than this _if_ I put time in redesigning PyArg_Parse. I would first like to take inventory of all the problems there are with PyArg_Parse, and then see whether we can design something that will solve most or all of these issues, without being overly complex in everyday use. And before I embark on that journey I would first like to have a group of people willing to put effort into this, plus the go-ahead of Guido (there's little point in designing a new mechanism if there is no chance of it being adopted as the general case, especially if this new mechanism may need a new PyMethodDef flag or some such thing). As a kickoff, here are some of my gripes about PyArg_Parse. 1. The format chars are arcane and without any logic. There is no logic to signed/unsigned type specifiers, some modifiers are suffixes (s#), some are different format chars (s versus z), some are prefixes (e). Everyone knows a basic set of 5 or 6 and has to look the rest up. Some types have special shortcuts without a clear rationale (String and Unicode are the only types to have an "O!", typename shortcut in the form of "S" and "U"). 2. There is conversion information interspersed with the argument list, for instance with O!, O& or es formats. This makes it very difficult to represent or build an argument parsing format in Python (this is worsened because some of the C objects in the argument list, such as the O& routine pointers, have no Python equivalent). And representing an argument list parser in Python is something that you need if you want to do dynamic wrapping of any kind (calldll, PyObjC, etc). 3. There is no way to create new, temporary objects during argument parsing, because there is no corresponding "release" call and no way to make the caller release new objects. Having temporary objects would make conversion a lot easier. Unicode and strings are the first types that come to mind, but there are probably others. 4. PyArg_ParseTupleAndKeywords makes the situation even worse. Each argument now has *three* different "index positions", the real index in the keyword list, a modified one in the format string (ignore all non-alphabetic chars and "e") and a third one in the argument list (ignore all extraneous arguments corresponding to es or O& or what-have-you). -- - Jack Jansen <Jack.Jansen(a)oratrix.com> http://www.cwi.nl/~jack - - If I can't dance I don't want to be part of your revolution -- Emma Goldman - [View Less]

3 2

Re: [Python-Dev] Mac OSX issues
by Michael Hudson Dec. 2, 2002

Dec. 2, 2002

Jack Jansen <Jack.Jansen(a)cwi.nl> writes: > I'm +0 on this. The reason I'm not +1 is that 2MB is just as > arbitrary as 1MB, Not quite; it's also the stack size passed to pthreads IIRC. So after ulimit -s 2048 all threads get the same stack size (I think). Cheers, M. -- 42. You can measure a programmer's perspective by noting his attitude on the continuing vitality of FORTRAN. -- Alan Perlis, http://www.cs.yale.edu/homes/perlis-alan/quotes.html

2 1

Re: [Python-checkins] python/dist/src/Python import.c,2.210,2.211
by Jack Jansen Dec. 2, 2002

Dec. 2, 2002

On vrijdag, nov 29, 2002, at 21:47 Europe/Amsterdam, jvr(a)users.sourceforge.net wrote: > Update of /cvsroot/python/python/dist/src/Python > In directory sc8-pr-cvs1:/tmp/cvs-serv20813/Python > > Modified Files: > import.c > Log Message: > Slightly improved version of patch #642578: "Expose > PyImport_FrozenModules > in imp". This adds two functions to the imp module: get_frozenmodules() > and set_frozenmodules(). Something that's been bothering me about … [View More]

4 3

Weekly Python Bug/Patch Summary
by Skip Montanaro Dec. 1, 2002

Dec. 1, 2002

Bug/Patch Summary ----------------- 313 open / 3091 total bugs (+4) 96 open / 1810 total patches (+2) New Bugs -------- __all__ not in RefMan index (2002-11-24) http://python.org/sf/643227 typo in Object/abstract.c : ternary_op (2002-11-24) http://python.org/sf/643260 Pythonwin : close() on a stdout (2002-11-25) http://python.org/sf/643571 New class special method lookup change (2002-11-25) http://python.org/sf/643841 ic module "path too long" error (2002-11-26) http://python.org/sf/… [View More]

1 0