[reportlab-users] Python baseline for ReportLab in 2003

[Tyler Eaves]

Well, here, we're running a mix of 2.x versions (Mainly 2.2 on my dev
machine, 2.1 everywhere else) so 2.2 might cause some minor issues, but
dropping 1.x support isn't a problem.

----- Original Message -----
From: "Andy Robinson" <andy@reportlab.com>
To: <reportlab-users@reportlab.com>
Sent: Monday, January 20, 2003 8:35 AM
Subject: [reportlab-users] Python baseline for ReportLab in 2003


> > If Python 1.5.2 compatibility is a goal (it's not
> > critical for my work), a simple backwards-compatible
> > idiom is to replace:
> >
> >   from XXX import YYY as ZZZ
> >
> > with:
> >
> >   from XXX import YYY; ZZZ=YYY; del YYY
> >
>
> IMHO we should fix this and then run a final batch
> of tests on 1.5.2, then officially 'draw a line' and say
> 1.18 is the last version to support 1.5.2.
>
> There are too many legacy 'conditional imports' and we
> are going to have to handle unicode strings as part of
> any rational approach to asian or middle eastern
> text support.  2.2.X will be around for some time
> and also offers many nice new things.
>
> Who would howl if we officially 'drew a line' soon
> and moved to 2.2 as our baseline?  We would still
> do 1.18.1, 1.18.2 etc for critical bugs but would not
> invest our own time in adding or backporting new features.
> Or, if anyone wants, we could let a volunteer maintain
> the compatible track with sourceforge checkin rights.
>
> Thanks,
>
> Andy Robinson
>
> _______________________________________________
> reportlab-users mailing list
> reportlab-users@reportlab.com
> http://two.pairlist.net/mailman/listinfo/reportlab-users