Am 24.04.2016 um 02:18 schrieb Leo Famulari:
> If we can successfully update to 3.5, that would be best. Otherwise, we
> should consider using 3.4.4.

I disagree.

While Python typically is backward-compatible (except for the big change
between Python 2 and Python 3), some minor incompatibilities are common
when upgrading from e.g. 3.4 to 3.5. E.g. in 3.5 some deprecated things
have been removed [1].

I suggest:

- Rename "python" (python@3.4.x) to "python-3.4"
- Add a new variable "python" as an alias for "python-3.4"
- Add "python-3.5" (@3.5.1) (for now independent from "python"
- Update python-3.4 to 3.4.5

So in feature we can easily provide two series (3.4, 3.5), which are
still available for those who need it. At the same time we can easily
switch "python" to the series we decide to be the "main" python for this
release. This is much like we already do for icedtea.

[1] https://docs.python.org/3.5/whatsnew/3.5.html#removed

-- 
Regards
Hartmut Goebel

| Hartmut Goebel          | h.goe...@crazy-compilers.com               |
| www.crazy-compilers.com | compilers which you thought are impossible |



Reply via email to