2008-09-30 18:43:38 Blair Zajac napisał(a):
> I'm not saying that for cross-platform work you need to find a Windows box.
>
> But if you're on Linux or Mac OS X and build Python 3.0 rcX from source which
> hasn't seen an official release yet, then presumably there's a Python 2.x on the
> system that you can test changes with.
I was testing the changes with Python 2.* before committing, but there wasn't
any traceback and I didn't try to build SWIG Python bindings, so I didn't notice
this problem.
(I have dev-lang/python-2.5.2-r7, dev-lang/python-2.6_rc2 and dev-lang/python-3.0_rc1.
They all were installed using Portage, Gentoo official package manager.)
> Greg Stein wrote:
> > Nope. That's never been the policy. Most of us don't have Windows
> > systems, so we have never been obligated to verify that our changes
> > remain compatible there.
> >
> > On Tue, Sep 30, 2008 at 9:33 AM, Blair Zajac <blair_at_orcaware.com> wrote:
> >> The advice I have is if one is making changes for a newer version of a
> >> dependency is to find a system or do a build that has the old version of the
> >> dependency and apply the diff to the old system to ensure it works. One
> >> ideally shouldn't have to rely upon other developers to catch these issues,
> >> the committer should take care to see that their changes are compatible with
> >> both systems.
> >>
> >> Blair
> >>
> >> Greg Stein wrote:
> >>> I see no reason to not make changes for additional compatibility. I did
> >>> examine one his constructs to ensure it remained compatible with 2.2.
> >>>
> >>>
> >>> On Sep 30, 2008, at 8:33, Eric Gillespie <epg_at_pretzelnet.org> wrote:
> >>>
> >>>> Greg Stein <gstein_at_gmail.com> writes:
> >>>>
> >>>>>>> Author: arfrever
> >>>>>>> Date: Sun Sep 28 08:06:24 2008
> >>>>>>> New Revision: 33335
> >>>>>>>
> >>>>>>> Log:
> >>>>>>> Python 3 compatibility:
> >>>> This "must support latest version" dance is really getting out of
> >>>> hand now.
--
Arfrever Frehtes Taifersar Arahesis
Received on 2008-10-01 14:56:54 CEST