Package: wnpp
Severity: wishlist
X-Debbugs-Cc: Debichem Team , Debian
Science List , debian-python@lists.debian.org
* Package name: mda-xdrlib
Version : 0.2.0
Upstream Contact: Irfan Alibay
* URL : https://github.com/MDAnalysis/mda-xdrlib
* License : PSF Licens
On 2024-07-22 11:40, Alexandre Detiste wrote:
Hi Nilesh,
I joined Astro team and took care of matplotlib rdeps there.
I'm struggling with basemap... I don't understand how
this multi-package with it's 3 setup.py works.
It's the very last rdpeps that will block migration later on.
I think it's
Package: wnpp
Severity: wishlist
Owner: Drew Parsons
X-Debbugs-Cc: debian-de...@lists.debian.org, debian-python@lists.debian.org
* Package name: pydantic-settings
Version : 2.1.0
Upstream Contact: Samuel Colvin
* URL : https://github.com/pydantic/pydantic-settings
Package: wnpp
Severity: wishlist
Owner: Drew Parsons
X-Debbugs-Cc: debian-de...@lists.debian.org, debian-python@lists.debian.org,
debian-scie...@lists.debian.org, debichem-de...@lists.alioth.debian.org
* Package name: custodian
Version : 2024.1.9
Upstream Contact: Shyue Ping Ong
On 2023-12-10 21:55, Kingsley G. Morse Jr. wrote:
Hi Rebecca, Julian and all science minded pythonistas of debian, great
and small!
3.) The following one-liner suggests 44 debian
packages might be affected by the breaks
Rebecca said would be caused by pandas 2.x:
$ for s in augur c
Package: wnpp
Severity: wishlist
X-Debbugs-Cc: debian-python@lists.debian.org, eam...@debian.org
Control: affects -1 src:fenics-basix
* Package name: scikit-build-core
Version : 0.5.1
Upstream Contact: Henry Schreiner
* URL : https://github.com/scikit-build/scikit-buil
Package: lintian
Version: 2.116.3
Severity: normal
X-Debbugs-Cc: debian-python@lists.debian.org
The current recommended way for packaging python packages (upstream)
is to provide a pyproject.toml file and build with setuptools
(python3-setuptools). Debian python package building activates this
bu
On 2023-01-17 18:12, Andreas Tille wrote:
Hi,
I upgraded the experimental branch of scipy to contain the submodules
upstream includes. I'm *not* convinced that we need them all -
hopefully we can get rid of boost (but upstream has some patches here)
and scipy-mathjax.
For the moment I've tried
Package: wnpp
Severity: wishlist
X-Debbugs-Cc: debian-python@lists.debian.org, Piotr Ożarowski
* Package name: accessible-pygments
Version : 0.0.2
Upstream Contact: Tania Allard
* URL : https://github.com/Quansight-Labs/accessible-pygments
* License : BSD
Pr
On 2022-09-03 20:08, Simon McVittie wrote:
Control: retitle -1 ITP: meson-python -- Meson PEP 517 Python build
backend
Control: owner -1 !
On Tue, 23 Aug 2022 at 01:25:49 +0200, Drew Parsons wrote:
* Package name: meson-python
Description : Meson PEP 517 Python build backend
I
Package: wnpp
Severity: wishlist
X-Debbugs-Cc: debian-python@lists.debian.org, Jussi Pakkanen
* Package name: meson-python
Version : 0.8.1
Upstream Author : Filipe Laíns
* URL : https://github.com/FFY00/meson-python
* License : MIT
Programming Lang: Python
Package: wnpp
Severity: wishlist
X-Debbugs-Cc: debian-python@lists.debian.org
* Package name: jupytext
Version : 1.13.8
Upstream Author : Marc Wouts
* URL : https://github.com/mwouts/jupytext
* License : MIT
Programming Lang: Python
Description : a plug
Package: wnpp
Severity: wishlist
X-Debbugs-Cc: debian-python@lists.debian.org
Control: affects -1 src:xhtml2pdf
* Package name: python-arabic-reshaper
Version : 2.1.3
Upstream Author : Abdullah Diab
* URL : https://github.com/mpcabd/python-arabic-reshaper/
* License
Package: wnpp
Severity: wishlist
X-Debbugs-Cc: debian-python@lists.debian.org, debian-scie...@lists.debian.org
* Package name: pyvista
Version : 0.32.0
Upstream Author : The PyVista Developers
* URL : https://github.com/pyvista/pyvista
* License : MIT
Programm
Package: wnpp
Severity: wishlist
Owner: Drew Parsons
X-Debbugs-Cc: debian-de...@lists.debian.org, debian-python@lists.debian.org,
debian-scie...@lists.debian.org
* Package name: python-npx
Version : 0.0.20
Upstream Author : Nico Schlömer
* URL : https://github.com
Package: wnpp
Severity: wishlist
X-Debbugs-Cc: debian-python@lists.debian.org
Control: affects -1 src:scipy
* Package name: python-sphinx-panels
Version : 0.6.0
Upstream Author : Chris Sewell
* URL : https://github.com/executablebooks/sphinx-panels
* License :
Package: wnpp
Severity: wishlist
X-Debbugs-Cc: debian-python@lists.debian.org, debian-scie...@lists.debian.org
* Package name: pythran
Version : 0.9.12
Upstream Author : Serge Guelton
* URL : https://github.com/serge-sans-paille/pythran
* License : BSD
Progra
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
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 extensions
(*_python*.so.) and could inject the pythons into Built-Using.
Package: wnpp
Severity: wishlist
X-Debbugs-Cc: debian-python@lists.debian.org
* Package name: python-cppimport
Version : 17.09.18
Upstream Author : Ben Thompson
* URL : https://github.com/tbenthompson/cppimport
* License : MIT
Programming Lang: Python
Descr
Package: wnpp
Severity: wishlist
X-Debbugs-Cc: debian-python@lists.debian.org
Control: block 962440 by -1
* Package name: python3-sphinx-sitemap
Version : 2.2.0
Upstream Author : Jared Dillard
* URL : https://github.com/jdillard/sphinx-sitemap
* License : MIT
Package: wnpp
Severity: wishlist
Owner: Drew Parsons
X-Debbugs-Cc: debian-de...@lists.debian.org, debian-python@lists.debian.org,
debian-scie...@lists.debian.org
* Package name: python-meshplex
Version : 0.13.2
Upstream Author : Nico Schlömer
* URL : https
Package: wnpp
Severity: wishlist
Owner: Drew Parsons
X-Debbugs-Cc: debian-de...@lists.debian.org, debian-scie...@lists.debian.org,
debian-python@lists.debian.org
* Package name: pygmsh
Version : 6.1.1
Upstream Author : Nico Schlömer
* URL : https://github.com
Package: wnpp
Severity: wishlist
X-Debbugs-Cc: debichem-de...@lists.alioth.debian.org,
debian-scie...@lists.debian.org, debian-python@lists.debian.org
Control: block 962440 by -1
* Package name: python-gsd
Version : 2.1.2
Upstream Author : Joshua A. Anderson et al, University of M
Package: wnpp
Severity: wishlist
Control: block 946035 by -1
Control: block 946451 by -1
* Package name: python-language-server
Version : 0.33.3
Upstream Author : Palantir Technologies, Inc
* URL : https://github.com/palantir/python-language-server
* License : M
On 2020-06-24 01:57, Stephan Lachnit wrote:
-BEGIN PGP MESSAGE-
Version: ProtonMail
wcFMAysU9YM04hChAQ//cTKRX2ovcrbEV2oEgObcf8/pwIk/p6l0K7sqm2Im
NHnk1mPaSg1VqIdK+QlqGgomxU/oZDSicnjRI1a7dNRvbJuOvMDKMqacQUIc
zJWXCdOxBw361ut+2LrcbwgaMFcW/fuXPbFFt3k5cWNVv8+qBtSFq/VwsSMs
Heh that's kind of
On 2020-06-23 09:55, Drew Parsons wrote:
Nice work. I can sponsor this.
Drew
On 2020-06-23 01:00, Stephan Lachnit wrote:
Package: sponsorship-requests
Severity: wishlist
Dear mentors,
I am looking for a sponsor for my package "symfit"
* Package name: symfit
Nice work. I can sponsor this.
Drew
On 2020-06-23 01:00, Stephan Lachnit wrote:
Package: sponsorship-requests
Severity: wishlist
Dear mentors,
I am looking for a sponsor for my package "symfit"
* Package name: symfit
Version : 0.5.2-1
Upstream Author : Martin Roelfs
*
Package: wnpp
Severity: wishlist
Control: block 962440 by -1
* Package name: python3-griddataformats
Version : 0.5.0
Upstream Author : Oliver Beckstein
* URL : https://www.mdanalysis.org/GridDataFormats/
* License : LGPL3+
Programming Lang: Python
Descripti
Package: wnpp
Severity: wishlist
Control: block 962440 by -1
* Package name: python3-mmtf
Version : 1.1.2
Upstream Author : Anthony Bradley
* URL : https://github.com/rcsb/mmtf-python
* License : Apache2
Programming Lang: Python
Description : binary enc
Package: wnpp
Severity: wishlist
Control: block 962442 by -1
* Package name: python3-msmb-theme
Version : 1.2.0
Upstream Author : Dave Snider
* URL : https://github.com/msmbuilder/msmb_theme
* License : MIT
Programming Lang: Python
Description : applies
Control: merge 955282 962341
thanks
Sorry, didn't check soon enough, Michael Crusoe is already working on
ruamel.yaml.clib.
Drew
Package: wnpp
Severity: wishlist
Owner: Drew Parsons
* Package name: ruamel.yaml.clib
Version : 0.2.0
Upstream Author : Anthon van der Neut
* URL : https://sourceforge.net/projects/ruamel-yaml-clib/
* License : MIT
Programming Lang: Python/C
Description
Package: wnpp
Severity: wishlist
Control: block 962268 by -1
* Package name: python3-palettable
Version : 3.3.0
Upstream Author : Matt Davis
* URL : https://jiffyclub.github.io/palettable/
* License : MIT-like
Programming Lang: Python
Description : a lib
Package: wnpp
Severity: wishlist
Control: block 962268 by -1
* Package name: monty
Version : 3.0.2
Upstream Author : Materials Virtual Lab
* URL : https://github.com/materialsvirtuallab/monty
* License : MIT
Programming Lang: Python
Description : the mis
Package: dh-python
Version: 4.20200315
Severity: normal
There are movements around upstream packages to stop using setup.py.
https://stackoverflow.com/questions/58753970/how-to-build-a-source-distribution-without-using-setup-py-file
PEP517 seems to be the culprit behind this movement,
https://py
Package: wnpp
Severity: wishlist
Owner: Drew Parsons
* Package name: pytest-mpi
Version : 0.3
Upstream Author : James Tocknell
* URL : https://github.com/aragilar/pytest-mpi
* License : BSD
Programming Lang: Python
Description : a plugin for pytest
Source: scipy
Followup-For: Bug #946625
Control: tags -1 help
The rules for skipping the failing tests
(test_sparsetools.TestInt32Overflow) are already in place in
debian/tests/python3
It looks like something must have changed in pytest such that the skip
instructions are now being ignored.
Need
Package: spyder
Version: 4.0.0~rc3+dfsg1-1
Severity: normal
spyder 4 (currently on salsa in experimental branch) needs python
modules python-language-server and qdarkstyle
These are currently not packaged for Debian, so this is a
Request For Help to get them packaged so we can proceed with the
sp
Alexandre MARIE a écrit:
I am trying to fix lmfit-py and python-fabio packages as the first
can't be built with python 3.8 and the second can't make it through
autopkgtest.
As I am not importing a new version but fixing one, I don't have the
orig.tar or debian.tar file and the error:
dpkg-sou
On 2019-10-27 23:13, Daniele Tricoli wrote:
On Sun, Oct 13, 2019 at 10:31:31PM +0800, Drew Parsons wrote:
It conditionally works. Using curl, I found that TLSv1_0 or TLSv1_1
will
support a successful connection, but only if the maximum SSL_VERSION
is
constrained to TLSv1_0 or TLSv1_1 (e.g
Daniele wrote:
I hope to have the time to investigate also this:
urllib3/contrib/pyopenssl.py
contains code to have SSL with SNI_-support for Python 2 and it depends
on
pyOpenSSL, cryptography and idna. Maybe looking at them can give us
more clues.
Also, could you see if using Python3 the con
Hi Daniele, just letting you know I uploaded python-urllib3 1.25.6 to
experimental.
I was having some SSL trouble connecting to https://pub.orcid.org. The
error trace cited urllib3/contrib/pyopenssl.py, so I downloaded and
installed python-urllib3 1.25.6 to see if updates to default SSL/TLS
Frederik wrote:
Hello, in one of my package (pymca), there is a syntax error like this.
byte-compiling
/builds/science-team/pymca/debian/output/pymca-5.5.2+dfsg/debian/python-pymca5/usr/lib/python2.7/dist-packages/PyMca5/Object3D/Object3DPlugins/ChimeraStack.py
to ChimeraStack.pyc
File
"/u
On 2019-09-12 22:46, Drew Parsons wrote:
https://python3statement.org/ is a site documenting the projects which
are supporting the policy of dropping Python2 to keep Python3 only.
The site is designed for python packages specifically, to have only
Python3 supported by end of 2020.
But it seems
On 2019-09-13 15:42, Andreas Tille wrote:
Hi,
as Peter Green found out the cloudpickle source package droped Python2
support which makes bug #938494 serious. I guess it would be even
harder to drop python-skimage right now since this would affect
python-numpy and according to
$ apt-cache rd
https://python3statement.org/ is a site documenting the projects which
are supporting the policy of dropping Python2 to keep Python3 only.
The site is designed for python packages specifically, to have only
Python3 supported by end of 2020.
But it seems to me it would be in the spirit of the
Hi Sandro, I've pushed a numpy patch that should allow pymca tests to
pass again (bugs #935454, #933056). Once pymca is running successfully
again, we'll be able to remove its python2.
I recommend uploading numpy 1:1.16.2-2 to help that along (probably
safer to patch 1.16 to fix these bugs bef
On 2019-09-03 11:56, Sandro Tosi wrote:
Within a given rdeps count it currently has secondary sorting made on
Bug No. It would polish off the forward deps if they could be used for
secondary sorting instead (highest number to lowest). Bonus points
for
making the headers clickable so the reader
On 2019-09-02 12:21, Sandro Tosi wrote:
On Sun, Sep 1, 2019 at 9:54 PM Drew Parsons
wrote:
Yes, your script counts the dependencies along one direction (rdeps),
identifying which packages are ready to be de-python2-ised next.
I'm talking about dependencies in the opposite direction, dep
On 2019-09-02, Sandro Tosi wrote:
On 2019-09-02 01:15, Drew Parsons wrote:
Sandro Tosi wrote:
i've prepared a small website,
http://sandrotosi.me/debian/py2removal/index.html, to keep track of
the bugs user-tagged `py2removal`.
It could be useful to add another column countin
Sandro Tosi wrote:
i've prepared a small website,
http://sandrotosi.me/debian/py2removal/index.html, to keep track of
the bugs user-tagged `py2removal`.
It could be useful to add another column counting the Dependencies in
the other direction.
i.e. for all the leaf packages ready for proces
Package: wnpp
Severity: wishlist
Owner: Drew Parsons
* Package name: python-pypathlib
Version : 0.1.2
Upstream Author : Nico Schlömer
* URL : https://github.com/nschloe/pypathlib
* License : MIT
Programming Lang: Python
Description : Polygon package
Package: wnpp
Severity: wishlist
Owner: Drew Parsons
* Package name: python-dmsh
Version : 0.1.3
Upstream Author : Nico Schlömer
* URL : https://github.com/nschloe/dmsh
* License : MIT
Programming Lang: Python
Description : simple mesh generator
On 2019-07-27 22:04, Drew Parsons wrote:
I've uploaded python-scipy 1.2.2 to unstable.
Previously the build system ran through distutils, but dh now gives an
error on that, and says pybuild should be used instead. So I
reorganised debian/rules to use dh --buildsystem=pybuild. I
I've uploaded python-scipy 1.2.2 to unstable.
Previously the build system ran through distutils, but dh now gives an
error on that, and says pybuild should be used instead. So I
reorganised debian/rules to use dh --buildsystem=pybuild. I also
reorganised rules to stop the second invocation o
Scott K wrote:
On 2019-07-24 09:01, eamanu15 . wrote:
El mar., 23 de jul. de 2019 a la(s) 21:55, Drew Parsons escribió:
What should "success" or completion look like on the tracker? I
uploaded pyfttw (not python-fftw, which is a different package)
hoping
to get the first line of
Scott Kitterman wrote:
See https://release.debian.org/transitions/html/python2-rm.html
The ones near the top of the stack (bottom of the page) are less likely
to
have rdepends that need to be sorted before action can be taken on
them.
What should "success" or completion look like on the tra
On 2019-07-07 23:31, Matthias Klose wrote:
On 07.07.19 16:55, Drew Parsons wrote:
On 2019-07-07 22:46, Mo Zhou wrote:
Hi science team,
By the way, when do we start dropping python2 support?
The upstreams of the whole python scientific computing
stack had already started dropping it.
Good
On 2019-07-07 22:46, Mo Zhou wrote:
Hi science team,
By the way, when do we start dropping python2 support?
The upstreams of the whole python scientific computing
stack had already started dropping it.
Good question. I think it is on the agenda this cycle, but
debian-python will have the cal
Ansgar wrote:
On Fri, 2019-05-03 at 19:49 +0800, Drew Parsons wrote:
> The first -g is the problem (in "-DNDEBUG -g -fwrapv -O2 -Wall").
Not sure about setup.py, but `-g0` (after `-g`) should also disable
debug information:
+---
| Level 0 produces no debug information at al
Dear Debian Python community,
how does one control or override the default flags used by setup.py
(setuptools module) when compiling a C extension for a python module?
The intention is to switch off -g in pygalmesh, because of memory
constraints on 32 bit systems when compiling against CGAL,
On 2019-03-17 02:48, Drew Parsons wrote:
Hi Dmitry, the Tools section still refers to git-dpm.
Ah, that would be MR-5, still in discussion.
On 2019-03-17 02:39, Dmitry Shachnev wrote:
On Fri, Mar 15, 2019 at 02:34:26PM +0100, Ondrej Novy wrote:
> https://salsa.debian.org/python-team/tools/python-modules/merge_requests/4
let's merge it without "Configurations" section now, please.
Done!
I will now also review the follow-up merge
On 2019-03-16 22:07, Paul Gevers wrote:
On 16-03-2019 13:48, Drew Parsons wrote:
Is there enough will to add more scipy patches for the buster release
to
reduce the remaining DeprecationWarnings? (they don't break tests,
they're just annoying)
Or should we just let it go at this
On 2019-03-11 14:39, Drew Parsons wrote:
I've adapted the 3 patches and pushed to salsa,
matrix_API_614847c5.patch
matrix_API_more_e0cfa29e2.patch
matrix_API_filter_check_87e48c3c5.patch
https://salsa.debian.org/python-team/modules/python-scipy/tree/master/debian/patches
...
On 2019-03-15 21:15, Ondrej Novy wrote:
Hi,
Thanks Ondrej, read and accepted.
welcome :)
Thanks :) I fixed scipy's test failures :)
The policy on Maintainer/Upload fields is interesting. I've
installed git-dpm, likely it will be useful for my other packages.
please don't use git-dpm i
On 2019-03-10 15:46, Drew Parsons wrote:
On 2019-03-10 03:51, Paul Gevers wrote:
Hi Drew,
To remove the deprecation warnings we'd need to deal with them at the
source. Upstream has patches
https://github.com/scipy/scipy/commit/614847c5fc8d5f8a618980df3c1b93540428ae46
https://githu
On 2019-03-10 03:51, Paul Gevers wrote:
Hi Drew,
On 08-03-2019 03:08, Drew Parsons wrote:
On 2019-03-07 20:46, Paul Gevers wrote:
If you upload now, your package will not migrate to testing before
the
full freeze becomes effective so it would need an unblock. If you
want
to fix this issue
On 2019-03-07 20:46, Paul Gevers wrote:
If you upload now, your package will not migrate to testing before the
full freeze becomes effective so it would need an unblock. If you want
to fix this issue with the three lines I saw in the bug report, you can
go ahead. However, it is probably worth wa
On 2019-03-07 22:07, Paul Gevers wrote:
Hi Drew,
On 07-03-2019 14:56, Drew Parsons wrote:
On 2019-03-07 20:46, Paul Gevers wrote:
However, it is probably worth waiting for a resolution of bug
915738 and combine it with that.
There hasn't been recent movement on 915738. I'll appl
On 2019-03-07 20:46, Paul Gevers wrote:
Hi Drew,
On 07-03-2019 13:19, Drew Parsons wrote:
python-scipy is currently failing all debci tests in both unstable and
testing.
autopkgtest only, so no FTBFS?
That's right, scipy builds fine.
Some of us want failing autopkgtest to be RC *
On 2019-03-07 19:00, Paul Gevers wrote:
Hi Drew,
On 07-03-2019 09:03, Andreas Tille wrote:
On Tue, Mar 05, 2019 at 07:01:54PM +0800, Drew Parsons wrote:
python-scipy has recently started failing all debci tests in testing
and
unstable, exacerbating the bug report in Bug#919929 [1].
The
python-scipy has recently started failing all debci tests in testing and
unstable, exacerbating the bug report in Bug#919929 [1].
The failing error is a MemoryError. But understanding the problem is
hampered by a flood of deprecation warnings, presumably triggered by
numpy 1.16. scipy 1.2 adde
>(gandi.net) recently changed
its webmail interface, but the new software doesn't handle Reply-To
addresses well. I've sent them a bug report.
On 2019-01-15 03:27, Drew Parsons wrote:
Hi Python team, now that numpy 1.16rc has reached testing, are there
plans to get scipy 1.2.0 into the c
On 2019-01-29 10:36, Dmitry Shachnev wrote:
On Mon, Jan 28, 2019 at 11:13:46AM +0100, webm...@emerall.com wrote:
Thanks Ondrej, read and accepted.
The policy on Maintainer/Upload fields is interesting.
I've installed git-dpm, likely it will be useful for my other
packages.
It will not be us
Hi Python team, now that numpy 1.16rc has reached testing, are there
plans to get scipy 1.2.0 into the coming release?
Will it help if I join DPMT? I can then update scipy and upload to
experimental. Please add me on salsa if that will help.
Drew
On Thu, 2018-02-22 at 12:11 +0100, Raphael Hertzog wrote:
> Hi,
>
> On Thu, 22 Feb 2018, Ondrej Novy wrote:
> > 2018-02-22 11:18 GMT+01:00 Drew Parsons :
> > > The python group on salsa does not have the button for joining
> > > the
> > > group (I don&
I updated xhtml2pdf to 0.2.1. But salsa is refusing to receive the
git push, "GitLab: You are not allowed to push code to this project.".
The python group on salsa does not have the button for joining the
group (I don't actually want to join the group, but the commits to
xhtml2pdf should be pus
79 matches
Mail list logo