Re: Python modules for every supported version

2004-06-15 Thread Terry Hancock
2.3. I'm sure there is one, of course, but I haven't run into it yet. Cheers, Terry -- Terry Hancock ( hancock at anansispaceworks.com ) Anansi Spaceworks http://www.anansispaceworks.com

Re: Python modules for every supported version

2004-06-15 Thread Terry Hancock
e to Python 2.3 and all is well. OTOH, Zope has actually moved past Python 2.1 -- versions 2.7+ use Python 2.3.4. Cheers, Terry -- Terry Hancock ( hancock at anansispaceworks.com ) Anansi Spaceworks http://www.anansispaceworks.com

Re: Correct location of .py and .pyc files

2003-11-18 Thread Terry Hancock
am > Yes. I don't know about future guarantees, but you may be assured that > it would be a Big Change if that were no longer true. Cheers, Terry -- Terry Hancock ( hancock at anansispaceworks.com ) Anansi Spaceworks http://www.anansispaceworks.com

Re: Correct location of .py and .pyc files

2003-11-18 Thread Terry Hancock
On Monday 17 November 2003 03:35 pm, Florent Rougon wrote: > Terry Hancock <[EMAIL PROTECTED]> wrote: > > There was some discussion on comp.lang.python about > > standardizing the bytecode awhile back, but the consensus > > was that the standardized part of Python is

Re: Correct location of .py and .pyc files

2003-11-17 Thread Terry Hancock
h them at all. There was some discussion on comp.lang.python about standardizing the bytecode awhile back, but the consensus was that the standardized part of Python is *the source code*. IMHO, they (/we) don't want to encourage obfuscated distributions of Python packages. Python is a very op

debconf

2003-09-13 Thread Terry Hancock
least. I've just started learning Debian packaging, and since I mostly work in Python, I'll likely be creating some python packages of software I already maintain or authored, at some point. Cheers, Terry -- Terry Hancock ( hancock at anansispaceworks.com ) Anansi S

Jython interp. problem.

2002-11-12 Thread Terry Hancock
and it works as I expected it to. I have also used Jython compiled from the upstream source. I figure it has to be something to do with the Debian packaging (and perhaps the choice of Java environment to run on). This is in the Debian 3.0r0 "Woody" distribution. Thanks for any ideas, Terry -- Terry Hancock ( hancock at anansispaceworks.com ) Anansi Spaceworks http://www.anansispaceworks.com