Hello Debian Python Team,
I would like to request for DPT salsa access so that I can work on
packages with the Python Team. I have a few packages that I would like
to work on and am currently packaging yte and its dependency dpath-python.
My salsa username is weepingclown. I have read the
While perfectly understanding the weak collaboration model reasoning, I've
still always found DPT as uploader and not maintainer rather absurd TBH. The
current go to tool (as I understand it) for python packaging, py2dsp, also
creates an initial packaging with team in uploaders section and the p
Hi Christian,
Improving docs is a very important thing, I appreciate your effort.
I quickly went through thr diff off your changes and it seems that you've
changed the wiki to mention that using quilt is not recommended. While gbp pq
is what the python team prefers indeed, the python team polic
Hi,
I have done the last two updates of python-mongoengine, and it is a module that
we use regularly at our work . So I can adopt python-mongoengine.
Best,
Ananthu
On 22 March 2024 7:18:49 am UTC, "Håvard F. Aasen"
wrote:
>Hi,
>
>I intend to orphan two of my team maintained packages, I am the
Hello Christian,
Without knowing what exactly fails for you, it is quite difficult to point out
anything. The steps documented in the wiki are supposed to be working.
That said, the current packaging go to tool for the DPT should be py2dsp, if
what you are working on is a python package. `apt i
Hi,
As an addendum, there is also dedicated wiki pages[0] intended to be of help to
newcomers. Not saying that solves everything mentioned before, but it does help
quite a lot. As I understand it, the current problem we have is more about the
wiki being less organized than there not being suffi
Hi,
I have always found most of issues mentioned in the thread a welcome change
instead, and if anything the far superior ability of apt to automatically
remove all the installed dependencies in case of the removal of a package
compared to the complete inability of pip has always left me in awe
Hi,
The ruby team has a similar ruby-team/mentors namespace for newcomers. That
works quite nicely.
Best,
Ananthu
On 13 June 2024 11:13:33 am UTC, "Pierre-Elliott Bécue" wrote:
>Andrey Rakhmatullin wrote on 13/06/2024 at 12:48:36+0200:
>
>> On Thu, Jun 13, 2024 at 07:28:32AM +0100, Phil Wyet
Hi,
I do support the idea of an IRC meeting. although the availability of others
(maybe even myself) is something I can't comment on. But I still think trying
this out, at the very least, would be nice. Hopefully this can be a catalyst
for finishing up the 3.12 migration. 3.13 migration is prob
Hi,
Thanks for bringing up this topic. #1064952 is something that goes well with
this discussion. I myself am an active user of pypi2deb and also have a pending
MR, and I'd love to see the package getting more attention. I am also very much
willing to contribute to improve the tooling. It makes
That'd be a nice thing to do. I believe there will already be
privacy-beach-generic complaints by lintian. The worst part is that they end up
appearing in all rdeps IIRC.
Best,
Ananthu
On 13 July 2024 10:19:43 pm UTC, Salvo Tomaselli wrote:
>Sorry for the OT, but should we consider patching mk
err, privacy breach*
On 14 July 2024 2:29:46 am UTC, weepingclown wrote:
>That'd be a nice thing to do. I believe there will already be
>privacy-beach-generic complaints by lintian. The worst part is that they end
>up appearing in all rdeps IIRC.
>
>Best,
>Ananthu
>
Hi,
This is a very reasonable thing to do considering the policy change. I also
have two packages where I mistakenly ended up as the maintaner and DPT as
uploader (see python-graphene-directives and python-graphene-federation)
because of tooling defaults and me missing to see it in the end. I h
Hi,
They were deprecated in 3.11 and will be removed in 3.13.
Best,
Ananthu
On 6 October 2024 5:17:51 pm UTC, Scott Kitterman wrote:
>Are these deprecated in 3.13 or removed?
>
2024 8:39:54 pm UTC, Soren Stoutner wrote:
>On Thursday, October 31, 2024 1:37:22 PM MST weepingclown wrote:
>That makes sense. I would recommend you update the Wiki with that wording.
Hi,
this is not entirely correct as while '-k' can be used to skip specific tests
with 'not ' it can also be used to only include tests matching a specific
pattern (in both cases it is just matching the pattern given). It is probably
better to rephrase it to something like "The `-k not ` flag c
Hi,
the file must not have been copied to the testbed, I assume. You can try adding
a debian/pybuild.testfiles file with vectors.json listed in it and that'd
*probably* take care of the issue.
Best,
Ananthu
It'd make sense to add that as additional info to the ITP bug thread so
that anyone interested in helping has some information on the current state.
And if my memory serves me right, uv mostly needed only uv specific internal
crates to be packaged than a lot of general ones.
Best,
Ananthu
On 29
Hi Peter,
I believe the previous way of doing this was -
override_dh_foo:
dh_foo
which is now less verbose if you want -
execute_after_dh_foo:
or execute_before, when you need that.
My understanding is that there is no added benefit than less verbosity and
maybe more clarity (s
Hi,
d/clean would work just as well, that's exactly what I tend to use if I have
more than a few files that I have to specify manually to be cleaned. And
personally, I'd recommend to use execute_after_dh_auto_clean than
override_dh_auto_clean so that it doesn't override anything it was previous
Hi,
Top of my head, there is src:pendulum and src:python-orjson. *Probably*
anything with a python3-maturin build-dep can be of help.
Best,
Ananthu
On 26 December 2024 2:55:07 pm UTC, Simon Josefsson wrote:
>Are there similar projects that are packaged in Debian that I look at
>for inspiration
21 matches
Mail list logo
