Re: Launchpad: Merge of Accounts Requested

Someone has asked us to merge one of your Launchpad accounts with another. If you go ahead, this will merge the account called 'Debian Python Modules Team (debian-python)' into the account 'johnfrandes12'. To confirm you want to do this, please follow this link: This looks extremely fishy - an

Re: sentry-python

Hi Eberhard, Is anyone working on updating sentry-python to prevent autoremoval due to #1058422 ? I did some debugging/testing, because this bug affects our Cura packages, but I didn't get very far. The root of

Re: Recommended way of installing system-wide python application and libraries

As far as how to do this within an existing cmake project, unfortunately, there doesn't seem to be a clear/easy way.  The only cmake example I can think off of the top of my head is cvc5.  It still uses setup.py though, so not a great future-looking example (and I had to patch it to build the P

Re: pybuild and optional dependencies

How can I teach pybuild that I really want xraylarch[larix] ? I don't know if there's a mechanism that can add optional dependencies automatically, but the easiest way would be to just add them to the Depends: ... or the Recommends: ... list of the respective package in debian/control.

Python module installation with cmake

Hi, I'm looking for help with a regression in cmake 3.27, that is currently producing incorrect module installation paths for the Python package Uranium: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042157 Uranium's cmake script uses the cmake variable Python_SITELIB to determine the i

Re: how to properly split up into python3-foo and foo-util package?

5) Not really 100% Debian related, but in the Python sdist,... should that contain the debian/*? No, and the upstream source shouldn't contain debian/ anyway, as the life cycles of packaging and upstream sources should be separate even if the person doing both is the same. This would then b

Re: Bug#1038883: dolfin: autopkgtest failure due to bytes as docstring

your package fails the autopkgtest with the new pytest 7.3 because python/test/unit/function/test_function_space.py uses a bytes object (b""" literal) as module docstring, and pytest crashes while looking for the "PYTEST_DONT_REWRITE" marker. This does sound like a serious bug in pytest, though.

Re: Lintian info message "hardening-no-bindnow" with vanilla debian/rules

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 having this hardening flag enabled is a good thing, it should probably be enabled

Re: Advice wanted: handling weird vendoring situation

> 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 script for updating the vendored >> dependencies? You could use that to find

Re: Advice wanted: handling weird vendoring situation

> 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 vendored code instead loads > this module to sys.modules["_pydev_imps._pydev_Sock

Re: Fixing pytest-twisted ^W Updating twisted

> Ignoring the autopkgtest for now Lintian is complaining about empty > binary packages for python3-twisted-{bin,dbg}. Are they needed anymore? > OTOH it's looking not that bad and a lot of the messages should be easy > to fix. > X: python3-twisted: library-package-name-for-application usr/bin/c

Re: Why is isal limited to just three archs?

> Did you look into the source package? isal is written in assembly > language... That doesn't seem quite right. The readme states: > other: > > Compiler: Portable base functions are available that build with most C > compilers. And it does look like there are corresponding .c implementations, a

Re: How should learning to program in Python be approached, if learning objectives are sought to be customised?

> Please also advise: where could I have such repositories like such > huge oracle java object and code repository? I think what most people use as a source for Python packages is PyPi: https://pypi.org/ And there is excellent tooling around it. Personally, I prefer pipenv for application depende

Re: How can I override module name in autopkgtest-pkg-python

> autopkgtest [19:46:36]: test autodep8-python3: set -e ; for py in > $(py3versions -r 2>/dev/null) ; do cd "$AUTOPKGTEST_TMP" ; echo "Testing with > $py:" ; $py -c "import cython_blis; print(cython_blis)" ; done > autopkgtest [19:46:36]: test autodep8-python3: [--- > Testing

Re: Packaging a python module when already using cmake buildsystem

> It has a setup.py and uses SetupTools and DistUtils so I was hoping to > add --with Python3 and hope that a lot of magic would be done by pybuild. > However as I'm already using cmake as the build system I can't stick > pybuild in there. We use both pybuild and cmake for a couple of SIP packages

Re: Issues when reading mailboxes from alioth-lists.debian.net

> File "/usr/lib/python3.8/mailbox.py", line 781, in get_message > msg.set_from(from_line[5:].decode('ascii')) > UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 37: > ordinal not in range(128) > Exit code: 1 > > IMHO it is a bug if those mailboxes can't be read. Am

Re: Best practice on how to package a python module along with a c++ program

>> I'm packaging a c++ program (horizon-eda) which also contains a >> python module written in c++. Upstream's Makefile has a target 'pymodule' >> and 'make pymodule' creates horizon.so in the build directory. >> According to upstream this has to be copied іnto python's sys.path > > The preferred m

Re: where should we put private libraries

>> You should consider /usr/lib// if you want to make your >> package multiarch-safe. > > And what about ? > > /usr/lib// > > whcih one is better ? Have a look at the Debian policy at https://www.debian.org/doc/debian-policy/ch-opersys.html#s-fhs It explicitly mentions: > Applications may also

Re: where should we put private libraries

> so my question is how can I solve this error. > I thought about adding rpath to these libraries in order to move then > under a private location /usr/lib/. But for this I need to add > an rpath to all the extensions which use these libraries. You should consider /usr/lib// if you want to make y

Re: Non-migration of cssutils

> If fixing those FTBFS is not on the table, I think you could just let it > be, and have it go out and then back in. Tricks like pinging the bug to > delay the autorm will likely backfire since it might very well be that > very same bug that is also removing calibre. At the same time, > botherin

python3-arcus only builds for python 3.8 despite pybuild

Hi, arcus is having some build/test issues related to Python 3.7 and 3.8: https://salsa.debian.org/3dprinting-team/libarcus/-/jobs/512109 In the built artifact, there is only a SIP module for python3.8, but autopkgtest only only installs python3.7: https://salsa.debian.org/3dprinting-team/libarcu

Re: Raising severity to serious for some Python 2 leaf packages with no Python 3 support upstream

Oh, and by the way, I just saw this: https://github.com/kovidgoyal/calibre/blob/master/README.python3 Perhaps a working Py3 port is not so far off after all.

Re: Raising severity to serious for some Python 2 leaf packages with no Python 3 support upstream

> As of now, calibre is not of sufficient quality to be part of a Debian release > and until it drops all Python2 requirements, it must be considered RC buggy. Is your quality argument based on the Calibre author's shenanigans? https://www.reddit.com/r/linux/comments/9wodtq/calibre_wont_migrate_to

Re: Streamlining the use of Salsa CI on team packages

> I am not a fan of pointing to a moving target with the "include" statement: > > include: > - https://salsa.debian.org/salsa-ci-team/pipeline/raw/master/salsa-ci.yml > - > https://salsa.debian.org/salsa-ci-team/pipeline/raw/master/pipeline-jobs.yml > > "master" will change, and that can br

Re: Ayuda para instalar python 3.7

> Para poder instalar py3.7 por default, tendrías que descargarlo desde > https://www.python.org/downloads/ > y ejecutar ```./configure && make && make install``` Alternatively, if you are patient, buster will become stable very soon. It comes with Python 3.7 by default.

ITP: python-hvac -- Python 2/3 client for HashiCorp Vault

Package: wnpp Severity: wishlist Owner: Gregor Riepl * Package name: python-hvac Version : 0.6.2 Upstream Author : Ian Unruh * URL : https://github.com/ianunruh/hvac * License : Apache-2.0 Programming Lang: Python Description : Python 2/3 client for

Re: RFS: mwic 0.7.4-1

> autopkgtest (debian/tests/) is a form of as-installed testing, which takes > the packages that were built, installs them in a relatively complete and > realistic environment (typically a lxc container or a qemu/kvm virtual > machine) and runs further tests there. Sometimes these tests just repeat

Re: RFS: mwic 0.7.4-1

> In case I've misunderstood you, and you're referring to unit tests > shipped debian/tests/*, than yes, I agree. :) As far as I understand, these tests are executed by the package builder after the upstream build script has finished. They're meant as a sort of integration test, i.e. "does this pa

RFS: hvac/0.5.0-1

Hi, I'd like to request sponsorship for the hvac Python module. Source package: hvac Packages: python-hvac, python3-hvac Version 0.5.0-1 Upstream: https://github.com/ianunruh/hvac Salsa: https://salsa.debian.org/python-team/modules/hvac Mentors: https://mentors.debian.net/package/hvac This packa

New package python-hvac / Joining the team

Hello, I'd like to join the DPMT to maintain a Debian package for hvac, a Python module that allows accessing Hashicorp Vault secrets remotely. The upstream project can be found here: https://github.com/ianunruh/hvac And the Debian package repository I created is here: https://github.com/onitake/d