23 Apr 12:20
[Trac-dev] Re: t.e.o updated to latest trunk
From: Christian Boos <cboos <at> neuf.fr>
Subject: [Trac-dev] Re: t.e.o updated to latest trunk
Newsgroups: gmane.comp.version-control.subversion.trac.devel
Date: 2008-04-23 10:20:14 GMT
Subject: [Trac-dev] Re: t.e.o updated to latest trunk
Newsgroups: gmane.comp.version-control.subversion.trac.devel
Date: 2008-04-23 10:20:14 GMT
Jeroen Ruigrok van der Werven wrote: > -On [20080422 20:48], Christian Boos (cboos <at> neuf.fr) wrote: > >> I think we can get a 0.11rc1 quite soon, then I'd said we can branch >> 0.11-stable and later we'll release 0.11 from that. >> > > Sounds fine by me. +1. > > >> For next week, I'll write a more detailed proposal about what we should >> do for 0.12, both for Trac itself and for the way we develop it. >> > > Sounds interesting, looking forward to it. > See Trac-users of this morning, for hints> >> OTOH, there's a huge pile of outstanding issues waiting in the 0.11.1 >> area (most prominent one being #3563), so we can find plenty things to >> do on branches/0.11-stable, while waiting for end of May... >> > > Right now the unittests for Python 2.3 fail for Trac. Part is due to > subprocess being imported, which is non-existent for 2.3. > That's for the functional tests. Well, those tests should simply be disabled when the appropriate supporting modules are not there (i.e. the same way it goes when twill is not present). On a related note, I wonder if we should continue support for 2.3, with so many newer Python releases out there (2.4 and 2.5 available for years, 2.6 coming soon, and 3.0 on the distant horizon). Given the memory issues with Genshi, I wouldn't even advise running Trac with Python 2.4. We can keep Python 2.3 compatibility on 0.11-stable, but we can now think about using 2.4 or even 2.5 features for upcoming versions. -- Christian --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Development" group. To post to this group, send email to trac-dev <at> googlegroups.com To unsubscribe from this group, send email to trac-dev-unsubscribe <at> googlegroups.com For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en -~----------~----~----~----~------~----~------~--~---
>
>> OTOH, there's a huge pile of outstanding issues waiting in the 0.11.1
>> area (most prominent one being #3563), so we can find plenty things to
>> do on branches/0.11-stable, while waiting for end of May...
>>
>
> Right now the unittests for Python 2.3 fail for Trac. Part is due to
> subprocess being imported, which is non-existent for 2.3.
>
That's for the functional tests. Well, those tests should simply be
disabled when the appropriate supporting modules are not there (i.e. the
same way it goes when twill is not present). On a related note, I wonder
if we should continue support for 2.3, with so many newer Python
releases out there (2.4 and 2.5 available for years, 2.6 coming soon,
and 3.0 on the distant horizon). Given the memory issues with Genshi, I
wouldn't even advise running Trac with Python 2.4. We can keep Python
2.3 compatibility on 0.11-stable, but we can now think about using 2.4
or even 2.5 features for upcoming versions.
-- Christian
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac Development" group.
To post to this group, send email to trac-dev <at> googlegroups.com
To unsubscribe from this group, send email to trac-dev-unsubscribe <at> googlegroups.com
For more options, visit this group at
RSS Feed