Hi Moritz (2020.10.16_18:33:06_+)
> > not ok. That would mean removing pypy3 from the archive as well. If you
> > don't
> > want to support Python2, then why do you care about it's removal for
> > bullseye+1?
>
> Ok. I assumed the need for Py2 in pypy3 was a temporary thing? If it's needed
>
> On 10/16/20 8:04 PM, Moritz Mühlenhoff wrote:
> > There will be few core packages build-depending on Python 2 (for tests
> > or building) which won't be ready for Python 3 for Bullseye (Chromium,
> > qtwebkit and IIRC also Pypy), but those only need Python 2 (and a very
> > small set of support p
On Fri, Oct 16, 2020 at 09:36:09PM +0300, Dmitry Shachnev wrote:
> Hi Moritz!
>
> On Fri, Oct 16, 2020 at 08:04:56PM +0200, Moritz Mühlenhoff wrote:
> > There will be few core packages build-depending on Python 2 (for tests
> > or building) which won't be ready for Python 3 for Bullseye (Chromium,
Hi Moritz!
On Fri, Oct 16, 2020 at 08:04:56PM +0200, Moritz Mühlenhoff wrote:
> There will be few core packages build-depending on Python 2 (for tests
> or building) which won't be ready for Python 3 for Bullseye (Chromium,
> qtwebkit and IIRC also Pypy), but those only need Python 2 (and a very
>
On Fri, Oct 16, 2020 at 08:21:09PM +0200, Matthias Klose wrote:
> > As such, I'd propose to include Python 2 (plus the small set of
> > support packages) in Bullseye
>
> ok. I think you should explicitly name all these packages.
Yeah. I think the final list is still TBD (e.g. depends on whether C
On 10/16/20 8:04 PM, Moritz Mühlenhoff wrote:
> There will be few core packages build-depending on Python 2 (for tests
> or building) which won't be ready for Python 3 for Bullseye (Chromium,
> qtwebkit and IIRC also Pypy), but those only need Python 2 (and a very
> small set of support packages li
6 matches
Mail list logo
