On Monday, August 22, 2016 at 1:14:35 PM UTC-7, Tim Graham wrote:
>
> I don't think releasing a new version of Trac and having it support a
> Python version whose support ends a few months later brings much value.
>
> Django adopted this policy, "Typically, we will support a Python version
>
I don't think releasing a new version of Trac and having it support a
Python version whose support ends a few months later brings much value.
Django adopted this policy, "Typically, we will support a Python version up
to and including the first Django LTS release whose security support ends
On Tue, Mar 15, 2016 at 5:30 PM, Tim Graham wrote:
> If Python 3 support for Trac won't be released until 2017, I think there's
> no need to support Python 3.3 which is end-of-life in September 2017
> (already the most recent release of Django supports Python 3.4+, for
>
If Python 3 support for Trac won't be released until 2017, I think there's
no need to support Python 3.3 which is end-of-life in September 2017
(already the most recent release of Django supports Python 3.4+, for
example). I think Python 3.5+ would be a fine target, but if people feel
that
Hi Ryan,
I am developping on windows where I use
- python 2.7 (with tools like django)
- C# (Visual Studio 2008) for some stuff,
- php (piwik)
- apache ( with a ntlm module to allow single sign on in out intranet)
- sometime python packages wich contain native C files
(which are compiled
On 3/15/16, RjOllos wrote:
> On Monday, March 14, 2016 at 12:28:32 PM UTC-7, anton wrote:
>
[...]
>
> What is your reason for wanting to run on Python 3.5?
>
[...]
I do not know about neither the OP intentions nor the roadmap and
goals for Trac Python 3 support but if I was
On Monday, March 14, 2016 at 12:28:32 PM UTC-7, anton wrote:
>
> Hi,
>
> this year I wanted to try to switch
> to python3.
>
> I tried to install packages on python 3.5.1
> - Genshi: worked
> - Babel: worked
> - Trac: I got a message thats its only pyton2 compatible
>
> So my little