On 03.11.19 15:09, Neil Williams wrote:
On Sun, 3 Nov 2019 15:00:17 +0100
Matthias Klose wrote:
[discussing this outside the bug report on the ML]
On 03.11.19 14:39, Neil Williams wrote:
Actually, that's a good catch. I was mixing up the defaults package
with the general advice on python3 mi
On Sun, 3 Nov 2019 15:00:17 +0100
Matthias Klose wrote:
> [discussing this outside the bug report on the ML]
>
> On 03.11.19 14:39, Neil Williams wrote:
> > Actually, that's a good catch. I was mixing up the defaults package
> > with the general advice on python3 migration to not remove
> > pyth
[discussing this outside the bug report on the ML]
On 03.11.19 14:39, Neil Williams wrote:
Actually, that's a good catch. I was mixing up the defaults package
with the general advice on python3 migration to not remove
python-foo-doc just to rename it to python3-foo-doc.
where did you read that
On 11/3/19 10:27 AM, Matthias Klose wrote:
> On 03.11.19 02:20, Paul Wise wrote:
>> On Sat, Nov 2, 2019 at 6:04 PM Matthias Klose wrote:
>>> Python2
>>> removal, or the introduction of Python 3.8. 3.8 also offers a
>>> central directory
>>> for bc files, so that's maybe another thing to look at, b
On 03.11.19 02:20, Paul Wise wrote:
On Sat, Nov 2, 2019 at 6:04 PM Matthias Klose wrote:
At this point I'd ignore any Python2 related package, and concentrate on Python3
stuff only.
Yes, I was referring only to python3-* module packages.
Byte compilation is an optimization, speeding up a pr
5 matches
Mail list logo
