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
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
Hi DPT,
I would like to join the Debian Python Team. I maintain the errbot
package, which is in my own namespace on salsa at the moment and which I
would like to move to the DPT namespace. Errbot is a chatbot for
multiple chat networks, written in Python.
In addition to that I started working
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
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 like setuptools/jinja) to build and
run their tests.
Hello,
Recently cherrytree [1] has been rewritten from Python to C++, thus it
no longer belongs in DPT. Could someone with adequate permissions
transfer it from DPT to generic Debian group on salsa.d.o?
Alternatively, one could grant me permission to manage cherrytree so as
I could transfer it
On 16/10/2020 09:19, Drew Parsons wrote:
On 2020-10-16 14:43, Giovanni Mascellani wrote:
Hi,
Il 16/10/20 02:53, Drew Parsons ha scritto:
Would it make sense to use the Built-Using [1] header?
...
[1]
On 10/15/20 10:03 PM, Alastair McKinstry wrote:
> On 15/10/2020 08:13, Giovanni Mascellani wrote:
>
>> Hi,
>>
>> Il 14/10/20 15:52, Alastair McKinstry ha scritto:
>>> I maintain the package "ecflow" which uses libboost-python-dev. Now
>>> with the transition to python3.9, ecflow will support
On 2020-10-16 14:43, Giovanni Mascellani wrote:
Hi,
Il 16/10/20 02:53, Drew Parsons ha scritto:
Would it make sense to use the Built-Using [1] header?
...
[1]
https://www.debian.org/doc/debian-policy/ch-relationships.html#additional-source-packages-used-to-build-the-binary-built-using
The
Hi,
Il 16/10/20 02:53, Drew Parsons ha scritto:
> Source: boost1.71
> Followup-For: Bug #972213
> X-Debbugs-Cc: debian-python@lists.debian.org
>
> Would it make sense to use the Built-Using [1] header?
> e.g.
> Built-Using: python3.8 python3.9
>
> dh_python3 knows if the module includes
11 matches
Mail list logo
