On Mon, Aug 25, 2008 at 9:18 AM, Ville M. Vainio [EMAIL PROTECTED] wrote:
Python 2.6 will probably be the earliest version that can be made
compatible with py3k (that's the explicit design choice of python
developers), so2.4as an interim requirement may not be worth it...
That may be
On Mon, Aug 25, 2008 at 3:08 AM, Edward K. Ream [EMAIL PROTECTED] wrote:
for very much longer. Python 2.4 is probably the earliest version
that can be make compatible with Python 3k, so pretty soon Python 2.4
will have to be the minimum.
Python 2.6 will probably be the earliest version that
On Mon, Aug 25, 2008 at 9:18 AM, Ville M. Vainio [EMAIL PROTECTED] wrote:
On Mon, Aug 25, 2008 at 3:08 AM, Edward K. Ream [EMAIL PROTECTED] wrote:
for very much longer. Python 2.4 is probably the earliest version
that can be make compatible with Python 3k, so pretty soon Python 2.4
will
I take it from the smiley that you're arguing a reductio ad absurdam:
RH7.3 includes Python 1.5.2.
- Stephen
On Aug 23, 8:44 am, Edward K. Ream [EMAIL PROTECTED] wrote:
On Fri, Aug 22, 2008 at 7:24 PM, thyrsus [EMAIL PROTECTED] wrote:
I represent only two users in my environment, and if
On Fri, Aug 22, 2008 at 7:24 PM, thyrsus [EMAIL PROTECTED] wrote:
I represent only two users in my environment, and if Python 2.4 must
be, you'll have to leave us behind for a while.
What's the earliest version of Python that you use? Maybe we'll make
that the minimum :-)
Edward
As part of the process of creating Leo3k (Leo for Python 3k), Leo now
requires Python 2.4 or higher.
Unlike previous versions, rev 880 of the trunk now properly puts up a
Tk dialog with the warning message. Previous versions of Leo crashed
because g.app.gui didn't exist. Rather than messing
I represent only two users in my environment, and if Python 2.4 must
be, you'll have to leave us behind for a while.
I'm the sysadmin for Unix compute servers and workstations used by
chip designers, and I use Leo to document/generate the OS
configuration (such as NFS mounts, package updates,
