On 1 juil. 2013, at 23:44, VernonCole wrote:
> Dropping support of 3.2 would potentially aid projects which have not yet
> converted to Python 3, since Python 3.3 supports u"Unicode Literals" but 3.2
> does not.
Third-party projects are free to set their own version requirements. For
instance
Debian Wheezy and Ubuntu 12.04 LTS are both on Python 3.2.
On Mon, Jul 1, 2013 at 5:44 PM, VernonCole wrote:
>
> Dropping support of 3.2 would potentially aid projects which have not yet
> converted to Python 3, since Python 3.3 supports u"Unicode Literals" but
> 3.2 does not. Skipping over the
Dropping support of 3.2 would potentially aid projects which have not yet
converted to Python 3, since Python 3.3 supports u"Unicode Literals" but
3.2 does not. Skipping over the early 3.x versions vastly eases transition
from 2.6 to 3.3.
Besides, what are the chances that someone running Pyt
On 1 juil. 2013, at 17:17, Peter Herndon wrote:
> So, there's a supported version of Python 2.7 and 3.3 for RHEL 6, which
> should make Python deprecation choices easier. I would suggest that the above
> link get some mention in the documentation, as this will make things much
> easier to sell
On 07/01/2013 10:34 AM, Clayton Keller wrote:
On 07/01/2013 10:17 AM, Peter Herndon wrote:
Hi all,
For those on RHEL6 or a derivative, please note that RHEL Software
Collections will provide an installation source for Python 2.7 and
3.3, as well as Postgres 9.2 and both MySQL 5.5 and MariaDB 5.
On 07/01/2013 10:17 AM, Peter Herndon wrote:
Hi all,
For those on RHEL6 or a derivative, please note that RHEL Software Collections
will provide an installation source for Python 2.7 and 3.3, as well as Postgres
9.2 and both MySQL 5.5 and MariaDB 5.5, and works for RHELs 6.2-6.4.
Furthermore,
Hi all,
For those on RHEL6 or a derivative, please note that RHEL Software Collections
will provide an installation source for Python 2.7 and 3.3, as well as Postgres
9.2 and both MySQL 5.5 and MariaDB 5.5, and works for RHELs 6.2-6.4.
Furthermore, "With the notable exception of Node.js, all Re
Hi,
On Friday, June 28, 2013 4:17:22 PM UTC+2, Aymeric Augustin wrote:
>
> As far as I can tell, there's a consensus on dropping support for Python
> 2.6. That will allow us to remove the vendored copy of unittest2 and to
> take advantage of datastructures introduced in Python 2.7 like OrderedDi
On 29 juin 2013, at 02:58, Ed Marshall wrote:
> RHEL7 beta (which, as luck would have it, should also ship with Python 3.3)
> won't land until end of year, at the earliest; I'd expect CentOS and SL to
> lag behind that a bit.
Which is perfectly timely: Django 1.7 will land roughly at that time
I agree that there is likely to be little overlap between people using old
systems and people using bleeding edge Django versions. Along the same lines,
it's worth noting that these users will have a supported version if Django
(1.6) for more than a year from today anyway.
Python 2.6 reminds me
Just to be clear: RHEL6 (which only ships Python 2.6) is the latest version
available right now. So, if you're a RHEL/CentOS/Scientific Linux shop,
you're either running Python 2.6, or you've rolled your own Python build.
(We have, but I assume we're slightly abnormal in that regard; upgrading
Djan
I also think the overlap between
1) People who want to always be running the absolute latest-released
cutting-edge versions of software, and
2) People who are running older editions of RHEL
...is likely to be rather small.
--
You received this message because you are subscribed to the Google Gr
Per the recent Red Hat Summit in Boston, RHEL7 willl be based off of Fedora
19, so yes: 2.7 will be the default /usr/bin/python in that distribution.
A related point of note: Python 2.6 is also easily installable on RHEL5 via
EPEL (parallel-installable with the Python 2.4 release that shipped with
On 06/28/2013 11:45 AM, charettes wrote:
If we drop support for Python 2.6 in Django 1.7 we should document that
1.6 will be the last version to support and announce it on the next
beta/candidate release.
Le vendredi 28 juin 2013 10:17:22 UTC-4, Aymeric Augustin a écrit :
Hello,
We jus
If we drop support for Python 2.6 in Django 1.7 we should document that 1.6
will be the last version to support and announce it on the next
beta/candidate release.
Le vendredi 28 juin 2013 10:17:22 UTC-4, Aymeric Augustin a écrit :
>
> Hello,
>
> We just forked the stable/1.6.x branch. The devel
Hello,
We just forked the stable/1.6.x branch. The development of Django 1.7
starts now!
As far as I can tell, there's a consensus on dropping support for Python
2.6. That will allow us to remove the vendored copy of unittest2 and to
take advantage of datastructures introduced in Python 2.7 like
16 matches
Mail list logo
