Hello,
I currently maintain send2trash, and it was suggested to me by Sandro
Tosi that I join the DPMT to team-maintain it. That sounds like an
excellent idea to me!
My salsa login is jdg
I have read and accept the DPMT policy.
Best wishes,
Julian
On Fri, Apr 02, 2021 at 10:55:10AM -0700, Otto Kekäläinen wrote:
> Hello Julian!
> I noticed that you've added me to several packages as the uploader:
> debian/control:
> Uploaders: Otto Kekäläinen ,
> Please do not do it. I have not reviewed/uploaded (to my knowledge) any of
> those
> package
On Fri, Sep 17, 2021 at 11:57:44PM +0200, Jochen Sprickerhof wrote:
> Hi,
>
> the Python language server packages where recently forked upstream (because
> the developers lost access to the original repos) and the development
> shifted there. I started working on new Debian packages for those (cf.
Hello!
pybuild is magic. It knows where the build directory is, despite it
seemingly calling setup.py with no command line arguments specifying
it!
But anyway, my actual question is this. How do I ensure that the data
files are also copied into the package? My package has a source tree
that lo
On Wed, Dec 01, 2021 at 01:32:38PM -0500, Louis-Philippe Véronneau wrote:
> On 2021-12-01 12 h 28, Andrey Rahmatullin wrote:
> >
> >> Only the .py files are currently included in the build; what is the
> >> best way to include all of the data files after the build step and
> >> before the test ste
On Tue, Jan 18, 2022 at 03:37:13PM +0100, Thomas Goirand wrote:
> On 1/17/22 18:47, Louis-Philippe Véronneau wrote:
> > Hey folks,
> >
> > I'm following up on bug #1001677 [1] on the DPT's list to try to reach
> > consensus, as I think the Lintian tags that were created to fix this bug
> > are not
Package: lintian
Version: 2.114.0
Severity: wishlist
X-Debbugs-Cc: Debian Python Team
I just hit two packages which gave me the following warning when
pkg_resources tried to load them:
/usr/lib/python3/dist-packages/pkg_resources/__init__.py:116:
PkgResourcesDeprecationWarning: 1.12.1-git202007
On Thu, Feb 03, 2022 at 11:34:26PM +0100, Pierre-Elliott Bécue wrote:
> Hi Michael,
>
> > Since Mistune 2.0.0 regresses its support for standard markdown, I ask
> > that a separate package be made for mistune 2.x to give more time for
> > mistune 0.8.x users to migrate to mistune 2.x or another l
On Fri, Feb 04, 2022 at 09:27:59PM +0530, Nilesh Patra wrote:
> On 2/4/22 9:18 PM, Julian Gilbey wrote:
> > Basically, the mistune upstream author has completely messed up on
> > this by making what is essentially a completely different package with
> > superficially similar
On Fri, Feb 04, 2022 at 09:27:59PM +0530, Nilesh Patra wrote:
> On 2/4/22 9:18 PM, Julian Gilbey wrote:
> > [...]
> > _mistune.py within the Debian package,
> > and have nbconvert do "import nbconvert.filters._mistune as mistune"
> > (see /usr/lib/py
Package: lintian
Version: 2.111.0
Severity: wishlist
X-Debbugs-Cc: debian-python@lists.debian.org
I just ran into several Python packages that install modules with
version number 0.0.0 because of some issue with their setup.py
scripts. I just did the following on my testing system:
lz4cat
/var/
On Sat, Feb 05, 2022 at 04:42:57PM -0500, Sandro Tosi wrote:
> > The test for this bug (and it should probably be recorded as an error,
> > not just a warning, as no Python package should have a version number
> > of 0.0.0)
>
> what exactly is the problem that would make it an 'error'?
When a pac
On Sun, Feb 06, 2022 at 04:46:53PM +, Stefano Rivera wrote:
> Hi Julian (2022.02.06_12:19:54_+)
> > In the couple of cases I've looked at so far, it is due to the
> > upstream version using use_scm_version in setup.py. This works fine
> > for a version that is in a Git repository, but it d
Hi,
I'm working towards packaging pydevd (which is a recursive dependency
of Spyder via IPython), and it's a somewhat challenging package! I
have hit an issue and would appreciate some thoughts on how best to
handle it.
Background:
pydevd is a debugging package which can attach to running scrip
On Tue, Feb 08, 2022 at 12:26:01AM +, Stefano Rivera wrote:
> Hi Julian (2022.02.07_06:26:38_+)
> > I'm a little confused by this. Have a look at
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005039 against
> > python3-iniconfig. It has a very straightforward debian/rules, using
On Mon, Feb 07, 2022 at 09:27:28PM +, Julian Gilbey wrote:
> [...]
>
> I thought I could address this issue by replacing the vendored copies
> of the library modules by symlinks to /usr/lib/python3.X/, but now
> I've hit another snag: some of these modules import other mo
Package: wnpp
Severity: wishlist
Owner: Julian Gilbey
X-Debbugs-Cc: debian-de...@lists.debian.org, debian-python@lists.debian.org
* Package name: python-bytecode
Version : 0.13.0
Upstream Author : Victor Stinner and
Matthieu C. Dartiailh
* URL
On Wed, Feb 09, 2022 at 07:39:40PM +0100, Gregor Riepl wrote:
> > I realise now that this "nice" solution won't work, as the standard
> > library code says:
> >
> > import socketserver
> >
> > so modifying sys.path will just change the value of
> > sys.modules["socketserver"]. However, the vendo
Package: wnpp
Severity: wishlist
Owner: Julian Gilbey
X-Debbugs-Cc: debian-de...@lists.debian.org, debian-python@lists.debian.org
* Package name: python-untangle
Version : 1.1.1+git20200807.fb916a9
Upstream Author : Christian Stefanescu
* URL : https://github.com
On Sun, Feb 13, 2022 at 12:07:44PM +0100, Gregor Riepl wrote:
> > So the solution I'm currently in the process of trying is to copy the
> > version from the oldest supported Python version at Debian package
> > build time. We'll see how this goes
> >
> >> Perhaps they have a maintenance scrip
I've just uploaded the latest version of QtPy (source: python-qtpy,
binary: python3-qtpy). But I'm disturbed by the dependency list.
QtPy is a wrapper for PyQt5, PyQt6, PySide2 and PySide6 providing a
uniform interface to these different packages. As such, setup.py
etc. do not specify a dependen
Well, the new version of qtpy failed the CI checks on armhf, and I
don't understand why. The cause is that the following caused an
error:
(sid_armhf-dchroot)jdg@abel:~$ python3
Python 3.10.4 (main, Apr 2 2022, 09:04:19) [GCC 11.2.0] on linux
Type "help", "copyright", "credits" or "license" for m
Hi Ghis,
On Thu, Apr 07, 2022 at 11:03:22AM +0200, ghisv...@gmail.com wrote:
> Hi Julian,
>
> Le mercredi 06 avril 2022 à 22:01 +0100, Julian Gilbey a écrit :
> > I've just uploaded the latest version of QtPy (source: python-qtpy,
> > binary: python3-qtpy). But I
On Fri, Apr 15, 2022 at 03:01:43PM +0100, Peter Michael Green wrote:
> But nowhere do I find any of QT_NO_OPENGL or QT_OPENGL_ES* defined in
> the package (but then maybe I'm not looking in the right place? So I
> don't know why these two classes are included in the amd64 version of
> the pack
On Mon, Apr 18, 2022 at 07:15:46PM +0200, Timo Röhling wrote:
> Hi,
>
> rstcheck used to be a pure CLI application, so I packaged it as
> "rstcheck" with a private module in /usr/share/rstcheck. The latest
> version has added a public module interface, so "import rstcheck"
> has become a thing and
Hi,
Somehow I managed to really mess up a commit to python-qtconsole: the
upstream and pristine-tar branches do not have the upstream/5.3.0
sources (the current ones). However, there's already an
upstream/5.3.0 tag in the repository, pointing to a commit to the
master branch.
I think the simples
On Sun, Apr 24, 2022 at 10:09:21PM +0200, Geert Stappers wrote:
> On Sun, Apr 24, 2022 at 09:01:02PM +0100, Julian Gilbey wrote:
> > Hi,
> >
> > Somehow I managed to really mess up a commit to python-qtconsole: the
> > upstream and pristine-tar branches do not have the
Hi Timo,
On Sun, Apr 24, 2022 at 10:42:51PM +0200, Timo Röhling wrote:
> Hi Julian,
>
> * Julian Gilbey [2022-04-24 21:01]:
> > Somehow I managed to really mess up a commit to python-qtconsole: the
> > upstream and pristine-tar branches do not have the upstream/5.3.0
>
On Sun, Apr 24, 2022 at 10:49:55PM +0200, Timo Röhling wrote:
> * Timo Röhling [2022-04-24 22:42]:
> > Make sure that your local upstream branch and the upstream/5.3.0 tag
> > both point at commit 08935221b549bf32157d739cd54eb1645a2ab123:
> Aaaand I copied the wrong commit hash to the email. :/
>
On Sun, Apr 24, 2022 at 10:49:55PM +0200, Timo Röhling wrote:
> * Timo Röhling [2022-04-24 22:42]:
> > Make sure that your local upstream branch and the upstream/5.3.0 tag
> > both point at commit 08935221b549bf32157d739cd54eb1645a2ab123:
> Aaaand I copied the wrong commit hash to the email. :/
>
Hi Timo (and Geert),
On Sun, Apr 24, 2022 at 10:42:51PM +0200, Timo Röhling wrote:
> Hi Julian,
>
> * Julian Gilbey [2022-04-24 21:01]:
> > Somehow I managed to really mess up a commit to python-qtconsole: the
> > upstream and pristine-tar branches do not have the upstr
On Tue, Apr 26, 2022 at 01:26:26PM +0200, Geert Stappers wrote:
> [...]
> > So the state of the salsa repository was (in an ideal world where I'd
> > pulled upstream):
> > - master included the upstream/5.3.0 commit, tagged as upstream/5.3.0,
> > along with further commits
> > - upstream was at u
Hi Timo,
On Tue, Apr 26, 2022 at 01:55:13PM +0200, Timo Röhling wrote:
> Hi Julian,
>
> * Julian Gilbey [2022-04-26 11:03]:
> > It turns out that I'd also messed up more than I'd realised: even when
> > I pulled in the updated master branch, I didn't pull th
Hi Julien,
On Thu, May 05, 2022 at 09:51:28AM +0200, julien.pu...@gmail.com wrote:
> Hi,
>
> I tried to update jupyter-core to 4.10.0, but didn't manage to run the
> upstream test suite reliably.
>
> I first disabled it, so the package was building with both dpkg-
> buildpackage and sbuild. A ba
On Thu, May 05, 2022 at 11:07:31PM +0200, julien.pu...@gmail.com wrote:
> Le jeudi 05 mai 2022 à 09:43 +0100, Julian Gilbey a écrit :
> >
> > I've had similar problems in the past. It usually comes down to the
> > build requiring some package that happens to be present
Dear Jonas,
I note that there is currently a serious bug against both
python-pytest-asyncio and pytest-mock
(https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006736), and this
bug is preventing the migration of several major packages to testing.
I also note that the current Debian version of pyt
Hi Jonas,
On Fri, May 27, 2022 at 01:11:45AM +0200, Jonas Smedegaard wrote:
> Hi Julian and other Pythonistas,
>
> Quoting Julian Gilbey (2022-05-27 00:44:22)
> > Currently python-pytest-asyncio is maintained just by you. I wonder
> > whether you would be willing to mo
Hi all,
When I updated pytest-mock, I noticed that pytest is somewhat out of
date and it would be good to upgrade it. But it's quite a major
package, and I don't really want to do it without a go-ahead from
others.
Perhaps we could upload a newer version to experimental first to see
what breaks?
On Thu, Jun 02, 2022 at 05:28:36PM +0200, julien.pu...@gmail.com wrote:
> Le jeudi 02 juin 2022 à 10:28 -0400, Sandro Tosi a écrit :
> > > I would suggest ratt-rebuilding all reverse dependencies. Could
> > > that be
> > > done?
> >
> > there order of thousands rdeps, i dont think it's fair to ask
On Sat, Jun 04, 2022 at 10:29:53AM +0800, Paul Wise wrote:
> On Fri, 2022-06-03 at 19:08 +0100, Julian Gilbey wrote:
>
> > I believe that ci.debian.net checks packages against packages in
> > experimental (see
> > https://ci.debian.net/packages/s/spyder/unstable/amd64/ for
Hi Ben,
On Mon, Jun 06, 2022 at 10:42:53PM -0400, Ben Westover wrote:
> > > _version.py is not a copy of versioneer, it's *generated* by versioneer.
> > > However, there is versioneer.py in the root directory, which is. I'll
> > > exclude that from the source and repack.
> >
> > hmm... how about
On Mon, Jun 06, 2022 at 09:01:37PM -0400, Sandro Tosi wrote:
> > > I think this page includes debci results for experimental:
> > >
> > > https://release.debian.org/britney/pseudo-excuses-experimental.html
> > >
> > > It shows what would happen when migrating experimental to unstable.
> >
> > Oh wo
On Tue, Jun 07, 2022 at 08:27:38AM +0100, Julian Gilbey wrote:
> > > Anyone willing to go for it?
> >
> > I thought you were volunteering for it? :) jokes aside, i think
> > preparing the new pytest upstream release for experimental may be the
> > "easiest
On Tue, Jun 07, 2022 at 09:47:33AM -0400, Antoine Beaupré wrote:
> On 2022-06-07 07:11:15, Julian Gilbey wrote:
> > [...]
> > As far as I understand, versioneer (or the _version.py generated by
> > it) uses a whole bunch of heuristics to determine the version number
> >
On Tue, Jun 07, 2022 at 10:51:08AM -0400, Antoine Beaupré wrote:
> It seems to me that generated files shouldn't be shipped as part of the
> source we distributed to users. Those files should be (re)generated at
> build time.
Ah, I understand you better now. Debian is full of generated files
dist
On Tue, Jun 07, 2022 at 09:47:14AM -0400, Antoine Beaupré wrote:
> >>> _version.py is not a copy of versioneer, it's *generated* by versioneer.
> >>> However, there is versioneer.py in the root directory, which is. I'll
> >>> exclude that from the source and repack.
> >>
> >> hmm... how about that
On Tue, Jun 07, 2022 at 03:59:22PM +0100, Julian Gilbey wrote:
> > > As far as I understand it, this file is used by the author of the
> > > program, not end users. I don't understand it well, though, because I
> > > haven't put much time into researching w
On Tue, Jun 07, 2022 at 03:49:37PM -0400, Sandro Tosi wrote:
> > Sandro: you managed the numpy transition, it seems. What is involved
> > in something like this? I would imagine something like:
> >
> > (1) Upload pytest 7.x to experimental
>
> i took care of this just now, uploading pytest/7.1.2
On Tue, Jun 07, 2022 at 03:49:37PM -0400, Sandro Tosi wrote:
> > Sandro: you managed the numpy transition, it seems. What is involved
> > in something like this? I would imagine something like:
> >
> > (1) Upload pytest 7.x to experimental
>
> i took care of this just now, uploading pytest/7.1.2
I'd like to ask for some help. I'm working on packaging pydevd, which
builds a private .so library. Ordinary extensions built using cython
or similar end up being called "foo.cpython-310-x86_64-linux-gnu.so",
but this library, which is not dependent on the Python version, should
presumably be cal
On Thu, Jun 09, 2022 at 11:23:26AM +0500, Andrey Rahmatullin wrote:
> On Wed, Jun 08, 2022 at 10:43:57PM +0100, Julian Gilbey wrote:
> > I'd like to ask for some help. I'm working on packaging pydevd, which
> > builds a private .so library. Ordinary extensions built us
On Thu, Jun 09, 2022 at 01:03:25PM +0500, Andrey Rahmatullin wrote:
> [...]
> > Well, the upstream wanted to compile two versions of the library, one
> > for 64 bit architectures and one for 32 bit architectures. I don't
> > really want to build two different arch libraries in a single build,
> >
On Thu, Jun 09, 2022 at 10:26:13AM +0100, Simon McVittie wrote:
> On Thu, 09 Jun 2022 at 13:03:25 +0500, Andrey Rahmatullin wrote:
> > The normal way for this is putting it into
> > /usr/lib//pkgname/foo.so, and according to the code below you'll
> > need the full path at the run time so you indeed
On Thu, Jun 09, 2022 at 11:00:28AM +0100, Simon McVittie wrote:
> On Thu, 09 Jun 2022 at 09:56:42 +0100, Julian Gilbey wrote:
> > OK (and yes, it does require the full path at runtime). What triplet
> > do I use in d/rules? dpkg-architecture offers 6 different ones:
> > D
On Thu, Jun 09, 2022 at 03:00:24PM +0500, Andrey Rahmatullin wrote:
> > The build system here is the standard Python setup.py, except for this
> > library. That is built by the following script:
> >
> > ---
> > g++ -m64 -shared -o attach_linux_amd64.so -fPIC -nostartfiles attach.cpp
> > mv attach
On Wed, Jun 15, 2022 at 09:30:56PM +0200, Carsten Schoenert wrote:
> Hi,
> [...]
> >
> > * monitoring-plugins-systemd 2.3.1-2
>
> I've updated sentry-python last week to the current upstream version, so
> this package can be count as fixed.
>
> Current pygments requires pytest >= 7.0, I've uploa
On Thu, Jun 23, 2022 at 02:00:21PM +0200, Felix Moessbauer wrote:
> Package: wnpp
> Severity: wishlist
> Owner: Felix Moessbauer
> X-Debbugs-Cc: debian-de...@lists.debian.org, debian-python@lists.debian.org
>
> * Package name: wnpp
> Version : 0.5.19
> [...]
> * URL : ht
On Wed, Jun 29, 2022 at 10:58:48AM -0400, Boyuan Yang wrote:
> Hi,
> [...]
> Thanks. I have uploaded an initial version to the NEW queue. The packaging
> work is at https://salsa.debian.org/python-team/packages/pdm-pep517/ .
>
> It is worth noting that I took the very aggressive way in stripping e
On Fri, Jun 24, 2022 at 06:53:04PM -0400, Louis-Philippe Véronneau wrote:
> Thank you for your guidance.
>
> I have filled all of the regressions you reported in the BTS:
>
> https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=pytest7;users=debian-python@lists.debian.org
Thanks Louis-Philippe!
Be
Dear all,
I wonder whether you might have any clue about
https://bugs.debian.org/1013700
I have mostly worked out the "cause" of the bug, but I haven't quite
got to the bottom of it.
When running the command
PYTHONPATH=. python3.10 -m pytest qtpy/tests
in the directory .pybuild/cpython3_3.10_qtpy
is required to perform a relative import
> for '.pybuild.cpython3_3.9_qtpy.build.qtpy.tests'
> /home/carles/git/python-qtpy
>
> Then let's try to avoid the initial "." confusion:
>
> $ mv .pybuild pybuild
> $ cd pybuild/cpython3_3.9_qtpy/build; python
st wishes,
Julian
On Mon, Jul 04, 2022 at 08:39:32PM +0100, Carles Pina i Estany wrote:
>
> Hi Julian,
>
> On Jul/04/2022, Julian Gilbey wrote:
> > Hi Carles,
> >
> > Thanks for your thoughts! Yes, indeed that seems to be the issue.
> >
On Thu, Jul 07, 2022 at 03:36:30PM -0400, Boyuan Yang wrote:
> Hi,
>
> 在 2022-06-28星期二的 11:19 -0400，Louis-Philippe Véronneau写道：
> > On 2022-06-28 09 h 24, Boyuan Yang wrote:
> > > Hi all,
> > >
> > > I have encountered more and more packages that uses pdm-pep517 as build
> > > backend. Looking at
Hi,
On Fri, Jul 08, 2022 at 09:33:10PM +0200, Carsten Schoenert wrote:
> Hi,
>
> Am 16.06.22 um 10:05 schrieb Julian Gilbey:
> ...
> > Great, thanks. Since the pygments in testing fails on pytest 7.2.1,
> > and the version in experimental depends on pytest >= 7.
Well, here's an update on this old thread...
On Thu, Jun 09, 2022 at 01:03:25PM +0500, Andrey Rahmatullin wrote:
> On Thu, Jun 09, 2022 at 08:42:28AM +0100, Julian Gilbey wrote:
> > > > I'd like to ask for some help. I'm working on packaging pydevd, which
> &
On Sun, Jul 24, 2022 at 11:46:14PM +0500, Andrey Rahmatullin wrote:
> On Sun, Jul 24, 2022 at 06:36:57PM +0100, Julian Gilbey wrote:
> > I got all of the triplets working, but was then stymied when I tried
> > to specify Multi-Arch: same in the control file. I got a lintian
>
On Sun, Jul 24, 2022 at 11:41:56PM +0500, Andrey Rahmatullin wrote:
> [...]
> >
> > I got all of the triplets working, but was then stymied when I tried
> > to specify Multi-Arch: same in the control file. I got a lintian
> > warning: multi-arch-same-package-calls-pycompile
> > It seems that sinc
On Mon, Jul 25, 2022 at 12:41:16AM +0500, Andrey Rahmatullin wrote:
> On Sun, Jul 24, 2022 at 08:30:42PM +0100, Julian Gilbey wrote:
> [...]
> > > > are they all effectively Multi-Arch: no? Is this worth thinking about
> > > > in the longer term?
> > > Wh
On Sat, Jul 23, 2022 at 07:52:19PM +0200, Louis-Philippe Véronneau wrote:
> Hey folks,
>
> We had a Python Team BoF at DC22 earlier today and I thought relaying the
> notes we took in gobby here would be a good idea.
Thanks for the notes, Louis-Philippe, and sorry I couldn't join you!
A few comm
On Sat, Jul 23, 2022 at 07:52:19PM +0200, Louis-Philippe Véronneau wrote:
> == pybuild improvements ==
>
> getting the autopkgtest MR in would be great
>
> https://salsa.debian.org/python-team/tools/dh-python/-/merge_requests/27
>
> We need people to test this MR some more, although it seems fai
On Tue, Jul 26, 2022 at 11:50:19AM -0300, Antonio Terceiro wrote:
> I think the notes did not capture the consensus correctly. The point was
> that it should be possible to automate updating the `Testsuite:` field
> to run tests with pybuild-autopkgtest, and that we should probably do
> that across
On Wed, Jul 27, 2022 at 10:26:33AM -0400, Louis-Philippe Véronneau wrote:
> The way I see it:
>
> 1. We should have a Lintian tag for packages not using the new
> pybuild-autodep8 autopkgtest. It would be even better if this tag would be a
> pointed hint that identified 'manually' written unit tes
On Wed, Jul 27, 2022 at 07:45:12PM +0100, Julian Gilbey wrote:
> On Wed, Jul 27, 2022 at 10:26:33AM -0400, Louis-Philippe Véronneau wrote:
> > The way I see it:
> >
> > 1. We should have a Lintian tag for packages not using the new
> > pybuild-autodep8 autopkgtest. It w
On Wed, Jul 27, 2022 at 09:32:19PM +0100, Julian Gilbey wrote:
> [...]
> >
> > I'd be wary about 2.2 and 2.3. I have several packages where I know
> > that an automated test will fail; there are all sorts of weird cases
> > [...]
>
> I'd be wary about
A question of curiosity: when I push a commit to salsa with a "Closes:
#n" in the changelog, the BTS gets a "tag: pending" notification.
I looked and looked, and could not find out how salsa does this?
Could anyone enlighten me? (The standard debian-ci scripts, which the
repositories use for t
Dear all,
I am intending to package a new dependency of textdistance called
rapizfuzz (along with its dependencies jarowinkler and rapizfuzz-capi,
and including rapizfuzz-cpp and jarowinkler-cpp within the packages).
It's relatively low priority though (and I haven't filed ITPs yet).
But it needs
On Sun, Aug 14, 2022 at 08:45:32AM +, Stefano Rivera wrote:
> Hi Julian (2022.08.14_07:18:49_+)
> > A question of curiosity: when I push a commit to salsa with a "Closes:
> > #n" in the changelog, the BTS gets a "tag: pending" notification.
> > I looked and looked, and could not find ou
On Sun, Aug 14, 2022 at 08:49:06AM +, Stefano Rivera wrote:
> Hi Julian (2022.08.14_07:41:26_+)
> > I don't know how many packages in Debian would be broken by the move
> > to 3.0.0; that may be something worth exploring. It may well be that
> > approach (2) makes most sense for the short
On Sun, Aug 14, 2022 at 11:38:10AM -0400, Sandro Tosi wrote:
> > It's a salsa webhook:
> > https://wiki.debian.org/Salsa/Doc#Dealing_with_Debian_BTS_from_commit_messages
> >
> > We don't have tooling that automatically configures all the repos, but
> > when we migrated to salsa, we set them all up
Hi!
A package I maintain within the team (python3-pyxdameraulevenshtein)
gives the following lintian message:
I: python3-pyxdameraulevenshtein: hardening-no-bindnow
[usr/lib/python3/dist-packages/pyxdameraulevenshtein.cpython-310-x86_64-linux-gnu.so]
The debian/rules file is very bland, essenti
On Tue, Aug 30, 2022 at 07:33:07PM +0200, Gregor Riepl wrote:
> > I: python3-pyxdameraulevenshtein: hardening-no-bindnow
> > [usr/lib/python3/dist-packages/pyxdameraulevenshtein.cpython-310-x86_64-linux-gnu.so]
> >
> > and there is nothing about CFLAGS or the like in the setup.py file.
> > So if
Package: wnpp
Severity: wishlist
Owner: Julian Gilbey
X-Debbugs-Cc: debian-de...@lists.debian.org, debian-python@lists.debian.org
* Package name: rapidfuzz-capi
Version : 1.0.5
Upstream Author : Max Bachmann
* URL : https://github.com/maxbachmann/rapidfuzz_capi
Package: wnpp
Severity: wishlist
Owner: Julian Gilbey
X-Debbugs-Cc: debian-de...@lists.debian.org, debian-de...@lists.debian.org,
debian-python@lists.debian.org
* Package name: rapidfuzz
Version : 2.6.1
Upstream Author : Max Bachmann
* URL : https://github.com
On Fri, Sep 09, 2022 at 10:00:49AM +0100, Julian Gilbey wrote:
> Package: wnpp
> Severity: wishlist
> Owner: Julian Gilbey
> X-Debbugs-Cc: debian-de...@lists.debian.org, debian-de...@lists.debian.org,
> debian-python@lists.debian.org
>
> * Package name: rapidfuzz
>
Package: wnpp
Severity: wishlist
Owner: Julian Gilbey
X-Debbugs-Cc: debian-de...@lists.debian.org, debian-python@lists.debian.org
* Package name: jarowinkler
Version : 1.2.1
Upstream Author : Max Bachmann
* URL : https://github.com/maxbachmann/JaroWinkler
* License
On Mon, Sep 19, 2022 at 01:52:09PM +0200, Iñaki Malerba wrote:
> [...]
> > Perhaps there's an opportunity to automate and getting wider CI usage.
>
> One of the biggest issues we had when a team adopted the pipeline was
> DDOSing of the instance because of the multiple pipelines generated when
> p
Package: wnpp
Severity: wishlist
Owner: Julian Gilbey
X-Debbugs-Cc: debian-de...@lists.debian.org, debian-python@lists.debian.org
* Package name: pylint-venv
Version : 2.3.0
Upstream Author : Jan Gosmann , Federico Jaramillo
* URL : https://github.com/jgosmann
I've been having a somewhat interesting time with the python3.11-add
transition. Python 3.11 has made some significant changes to its
bytecode representation, and also changed some of it's internal data
structures related to frames quite significantly.
In my corner of the Python world, several im
Dear all,
A strange one. I've uploaded pydevd version 2.9.2+ds-4 to unstable.
It turned out that many of the package tests fail on s390x with Python
3.11 but pass on all of the other architectures. I really don't
understand the internals of the package (it's pretty low-level stuff)
and I have no
On Tue, Nov 22, 2022 at 09:22:05AM +0100, Thomas Goirand wrote:
> > this, 100 times
>
> I very much don't agree. I think it's going pretty well, and the number of
> breakage isn't high. We just need a little bit of effort to make it in good
> enough shape.
> [...]
> Now, out of *many* of my packag
On Tue, Nov 22, 2022 at 05:01:03PM +0100, Thomas Goirand wrote:
> > If there are people with the expertise to help upstream update
> > bytecode and parso (and probably several other low-level packages) for
> > 3.11 so that the software that depends on them works with 3.11, then
> > fine. (And it i
On Wed, Nov 23, 2022 at 12:21:38AM +0100, Thomas Goirand wrote:
> On 11/22/22 17:59, Julian Gilbey wrote:
> > > > Or should we mark them as X-Python3-Version: << 3.11 so they can stay in
> > > > testing as long as Python 3.10 is the default?
> > >
> &g
On Mon, Dec 05, 2022 at 06:24:48AM +, Guðjón Guðjónsson wrote:
> Hi list
> I am working on eric and I made a mistake while updating the git repository.
> Some paths have changed so files were not excluded correctly and now upstream
> and pristine-tar contain jquery*.js files.
> How can I remove
Hi Graham,
On Mon, Dec 12, 2022 at 11:51:11PM +, Graham Inggs wrote:
> Dear Python Team
>
> Looking at the current state of the 'adding Python 3.11 as a supported
> version' transition [1], the tracker [2] shows only 12 red packages
> (excluding unknowns and packages not in testing) remaining
On Thu, Dec 15, 2022 at 04:10:05PM +0100, Thomas Goirand wrote:
> On 12/13/22 13:34, Julian Gilbey wrote:
> > If Python 3.11 is the default, then it is highly likely that Spyder
> > will not be included: debugpy, which is a dependency of Spyder and
> > python3-ipykernel (an
On Sun, Dec 18, 2022 at 06:02:58PM +, Julian Gilbey wrote:
> On Thu, Dec 15, 2022 at 04:10:05PM +0100, Thomas Goirand wrote:
> > On 12/13/22 13:34, Julian Gilbey wrote:
> > > If Python 3.11 is the default, then it is highly likely that Spyder
> > > will not be in
Hi Jochen,
On Mon, Dec 19, 2022 at 04:53:58PM +0100, Jochen Sprickerhof wrote:
> Hi Julian,
>
> * Julian Gilbey [2022-12-19 09:41]:
> > Quick update: with the updating of python3-bytecode from 0.13 to 0.14
> > in unstable/testing, which allows it to handle Python 3.11, some
On Thu, Jan 05, 2023 at 07:14:40PM +, Guðjón Guðjónsson wrote:
> Hi list
> I am working on eric and I do have a problem with the lintian requirement to
> replace the jquery.js file with the debian provided jquery.js file.
> The upstream author pointed out that it doesn't work as well and I have
On Sat, Jan 14, 2023 at 07:34:59PM +, Scott Kitterman wrote:
> Typically though doesn't the python interpreter package provide modules that
> are now incorporated? If python3.11 provides python3-tomli, won't that mess
> this up?
In this case, it doesn't; the Python 3.11 standard library mod
On Mon, Jan 16, 2023 at 05:05:39PM +0100, Andreas Tille wrote:
> Hi,
>
> I tried to create a multi-source tarball for scipy in its experimental
> branch[1]. Upstream includes a set of git submodules in its build
> process. I intended to merge all these submodules in a single
> scipy_1.10.0.orig-
1 - 100 of 220 matches
Mail list logo
