Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.maint.python > #8025 > unrolled thread
| Started by | Scott Kitterman <debian@kitterman.com> |
|---|---|
| First post | 2015-12-31 10:50 +0100 |
| Last post | 2016-01-04 17:10 +0100 |
| Articles | 3 — 3 participants |
Back to article view | Back to linux.debian.maint.python
Switching Default Python3 To Python3.5 Scott Kitterman <debian@kitterman.com> - 2015-12-31 10:50 +0100
Re: Switching Default Python3 To Python3.5 Matthias Klose <doko@debian.org> - 2016-01-01 22:20 +0100
Re: Switching Default Python3 To Python3.5 Barry Warsaw <barry@debian.org> - 2016-01-04 17:10 +0100
| From | Scott Kitterman <debian@kitterman.com> |
|---|---|
| Date | 2015-12-31 10:50 +0100 |
| Subject | Switching Default Python3 To Python3.5 |
| Message-ID | <qLI1P-2JG-1@gated-at.bofh.it> |
I went through the bad/unknown packages in the python3.5 transition tracker [1] and the remainder seems reasonable for doing the transition. Many of them only build support for the default python3 and so they will be bad until after they are rebuilt following the switch. I filed bugs with patches for packages that seemed to be ~easy to make build for multiple versions. Some of the remainder should not be build-depending on python3-dev at all since they don't have any arch specific content. I filed a stack of bugs on those too (as well as doing a team upload or two). That should leave in the neighborhood of 45 - 50 binNMUs, which isn't so many. Does anyone object if I go ahead and ask the release team for a transition slot? [1] https://release.debian.org/transitions/html/python3.5.html
[toc] | [next] | [standalone]
| From | Matthias Klose <doko@debian.org> |
|---|---|
| Date | 2016-01-01 22:20 +0100 |
| Message-ID | <qMfh7-7Dn-1@gated-at.bofh.it> |
| In reply to | #8025 |
On 31.12.2015 10:44, Scott Kitterman wrote: > I went through the bad/unknown packages in the python3.5 transition tracker > [1] and the remainder seems reasonable for doing the transition. > > Many of them only build support for the default python3 and so they will be > bad until after they are rebuilt following the switch. I filed bugs with > patches for packages that seemed to be ~easy to make build for multiple > versions. > > Some of the remainder should not be build-depending on python3-dev at all > since they don't have any arch specific content. I filed a stack of bugs on > those too (as well as doing a team upload or two). > > That should leave in the neighborhood of 45 - 50 binNMUs, which isn't so many. > > Does anyone object if I go ahead and ask the release team for a transition > slot? No. However there is a real issue with ipython. For Ubuntu xenial I just disabled the tests. It would be nice if ipython would have an update strategy, whether this is the 2.x, 3.x or the 4.x branch. Matthias
[toc] | [prev] | [next] | [standalone]
| From | Barry Warsaw <barry@debian.org> |
|---|---|
| Date | 2016-01-04 17:10 +0100 |
| Message-ID | <qNfRM-5IQ-9@gated-at.bofh.it> |
| In reply to | #8025 |
On Dec 31, 2015, at 04:44 AM, Scott Kitterman wrote: >Does anyone object if I go ahead and ask the release team for a transition >slot? +1 and thanks! -Barry
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.maint.python
csiph-web