Yes, I think we would do that. We went to a lot of trouble to release
0.6.7 with Python 2.4 support before we dropped it, and it worked out,
so I think it's a good plan for future Python version support drops
(which shouldn't be nearly as hard, until we drop Python 2 support).
Aaron Meurer
On Th
On Thu, May 24, 2012 at 6:06 PM, Joachim Durchholz wrote:
> Executive summary:
>
> From my perspective, I think that
> - the language and stdlib changes of 2.6 would be Nice To Have (TM)
> - the security issues are relevant enough to warrant dropping 2.5
> - the case for keeping 2.5 is user base.
People should be warned in good time, to have time to switch. ¿What
about announcing that next released version will have 2.5 support, but
after that it will be dropped?
Kjetil
On Thu, May 24, 2012 at 8:06 PM, Joachim Durchholz wrote:
> Executive summary:
>
> From my perspective, I think that
>
Executive summary:
From my perspective, I think that
- the language and stdlib changes of 2.6 would be Nice To Have (TM)
- the security issues are relevant enough to warrant dropping 2.5
- the case for keeping 2.5 is user base.
Do we have data that allows us to judge its relevance?
Am 25.05.20
On Thu, May 24, 2012 at 10:35 PM, Joachim Durchholz wrote:
> Am 24.05.2012 21:26, schrieb Aaron Meurer:
>
>> Note that the main reason to keep Python 2.5 support would be for
>> people who don't have enough control over their system to install or
>> compile Python 2.6 or 2.7.
>
>
> Now I'm curious
On Thu, May 24, 2012 at 9:29 PM, Aaron Meurer wrote:
> On Thu, May 24, 2012 at 11:22 AM, Sergiu Ivanov
> wrote:
>> On Thu, May 24, 2012 at 6:59 PM, Sergiu Ivanov
>> wrote:
>>> On Thu, May 24, 2012 at 1:52 PM, Vladimir Perić
>>> wrote:
Currently, we do support Python 3, but only with
Am 24.05.2012 21:26, schrieb Aaron Meurer:
Note that the main reason to keep Python 2.5 support would be for
people who don't have enough control over their system to install or
compile Python 2.6 or 2.7.
Now I'm curious: What difference between 2.4 and 2.5 is making 2.4
support-unworthy and 2
On Thu, May 24, 2012 at 10:29 PM, Aaron Meurer wrote:
> On Thu, May 24, 2012 at 11:22 AM, Sergiu Ivanov
> wrote:
>>
>> Just one more question: in the py3k-sympy directory I get after
>> running use2to3 I cannot run ./bin/isympy because of
>>
>> File "./bin/isympy", line 175
>> print __doc__ #
On Thu, May 24, 2012 at 11:22 AM, Sergiu Ivanov
wrote:
> On Thu, May 24, 2012 at 6:59 PM, Sergiu Ivanov
> wrote:
>> On Thu, May 24, 2012 at 1:52 PM, Vladimir Perić
>> wrote:
>>>
>>> Currently, we do support Python 3, but only with the use of the 2to3
>>> tool (vie the bin/use2to3 script). As su
Note that the main reason to keep Python 2.5 support would be for
people who don't have enough control over their system to install or
compile Python 2.6 or 2.7.
Aaron Meurer
On Thu, May 24, 2012 at 2:06 AM, krastanov.ste...@gmail.com
wrote:
> If this is a vote, I vote for dropping 2.5.
>
> The
On Thu, May 24, 2012 at 6:59 PM, Sergiu Ivanov
wrote:
> On Thu, May 24, 2012 at 1:52 PM, Vladimir Perić wrote:
>>
>> Currently, we do support Python 3, but only with the use of the 2to3
>> tool (vie the bin/use2to3 script). As such, the recommended
>> development process is to work in Python 2. t
On Thu, May 24, 2012 at 1:52 PM, Vladimir Perić wrote:
>
> Currently, we do support Python 3, but only with the use of the 2to3
> tool (vie the bin/use2to3 script). As such, the recommended
> development process is to work in Python 2. then once everything is
> alright run use2to3 and check if all
On Thu, May 24, 2012 at 12:36 PM, Sergiu Ivanov
wrote:
> Hello,
>
> I have seen it mentioned a number of times in various places that
> SymPy fully supports Python 3 (I hope I'm not mistaken), and,
> obviously, SymPy supports Python 2.7. Since I am going to write quite
> a bit of code, what shoul
Hello,
I have seen it mentioned a number of times in various places that
SymPy fully supports Python 3 (I hope I'm not mistaken), and,
obviously, SymPy supports Python 2.7. Since I am going to write quite
a bit of code, what should be my strategy with respect to Python
versions? Is it a good ide
If this is a vote, I vote for dropping 2.5.
The app engine does support 2.7. You can not install 2.5 in the
latests debian (from the official repos). If you are stuck on an old
platform compiling 2.7 in home is *extremely* easy (you must have
gcc).
--
You received this message because you are su
One of the main reasons to keep 2.5 support was for the App Engine,
but I believe it now supports 2.7. I don't know of any major features
from 2.6 that we're missing. I guess you could check the compatibility
file to get an idea. I know it's not even close to the way it was with
2.4. I couldn't wai
I just visited the python.org website and found that 2.5 does not get
security fixes anymore. The last release was in May 26th, 2011.
What's the policy for which Python versions SymPy should support?
Possible reasons to keep 2.5 support:
Note that it is possible to run unsafe software if you
17 matches
Mail list logo
