ere I switch python version several
> > times a day (and venv several times an hour).
> > For now, I use conda instead but it is slow (mamba is better) and uses a
> > lot of disk space.
>
> You don't need it packaged to use it.
Anyway, pyenv is in the NEW queue:
https:/
it is set
> to upstream).
>
> I am the package maintainer.
I could not make you Owner, but I made you Maintainer and updated the default
branch.
--
Dmitry Shachnev
signature.asc
Description: PGP signature
Hi Thomas!
On Thu, Feb 20, 2025 at 02:19:58PM +0100, tho...@goirand.fr wrote:
> On Feb 20, 2025 11:21, Dmitry Shachnev wrote:
> > amp is not in testing and has 2 RC bugs (other than one about nose), so
> > I think we do not need to care about it.
>
> I wish you w
, but in my opinion keeping nose just for one or
two packages is not worth the effort.
I would get it removed, and after that someone can package pynose (a fork) if
they need it.
--
Dmitry Shachnev
signature.asc
Description: PGP signature
, not from the target
installation directory. So setuptools does not copy all files there.
--
Dmitry Shachnev
signature.asc
Description: PGP signature
e distributions [2] which says that rules are the same.
[1]:
https://packaging.python.org/en/latest/specifications/binary-distribution-format/#escaping-and-unicode
[2]:
https://packaging.python.org/en/latest/specifications/source-distribution-format/#source-distribution-file-name
--
Dmitry Shachnev
signature.asc
Description: PGP signature
not convinced that we need to update nose package to pynose
upstream. However, if pynose has some patches that help us, we can always
cherry-pick them (maybe after updating debian/copyright).
That said, https://bugs.debian.org/1080224 is not fixed in pynose. Or at
least the problematic line is st
]:
https://sources.debian.org/src/python-mkdocs/1.5.3%2Bdfsg-1/debian/scripts/dh_mkdocs/#L146
--
Dmitry Shachnev
signature.asc
Description: PGP signature
ckaged
version [1]. Perhaps you can make it replace more libraries the same way.
[1]:
https://salsa.debian.org/python-team/packages/python-mkdocs/-/blob/debian/master/debian/scripts/dh_mkdocs?ref_type=heads#L148-L149
--
Dmitry Shachnev
signature.asc
Description: PGP signature
3].
Maybe you can use any of these two approaches in your package, too.
[1]: https://github.com/Python-SIP/sip/pull/28
[2]: https://setuptools-scm.readthedocs.io/en/latest/usage/#git-archives
[3]: https://github.com/Python-SIP/sip/pull/30
--
Dmitry Shachnev
signature.asc
Description: PGP signature
basic_layout.html tried to extend itself, which caused
a recursion error.
I pushed a fix and the build job succeeded now. build-i386 failed, but that
one is not related to Sphinx.
--
Dmitry Shachnev
signature.asc
Description: PGP signature
[1]: doc/sphinx/theme/sphinx13/*
[2]:
https://github.com/lmfit/lmfit-py/commit/29e4712036606913149e16b246340a7fbedd8829
[3]:
https://github.com/lmfit/lmfit-py/commit/e2418377c9870e02c820d0fe40d2232187864a81
[4]:
https://github.com/sphinx-doc/sphinx/commit/8e730ae303ae686705ea12f44ef11da926a8
was a way
> to opt out of this behavior.
I have seen a similar problem in https://bugs.debian.org/1052802 and solved
it by disabling dh_auto_clean completely.
I agree, it would be nice if pybuild did not delete .egg-info directories
inside tests, or provided a way to opt out.
--
Dmitry
backported:
- sip6 (although, it may conflict with sip5 from oldstable)
- pyqt-builder
- pyqt6-sip
--
Dmitry Shachnev
signature.asc
Description: PGP signature
that because I thought I wouldn't have time to figure out
> before next week (as I'm taking days off starting tomorrow morning), but it
> looks like everything is fine now... :)
Thank you!
--
Dmitry Shachnev
signature.asc
Description: PGP signature
t's there but dh_sphinxdoc still shows this error, then it's probably a
dh_sphinxdoc bug. Otherwise, please figure out why that line is not there.
> So please don't re-open bugs, I'll take care of that next week, and just
> fixing the docs theme should fix it.
OK.
--
Dmitry Shachnev
signature.asc
Description: PGP signature
Hi Thomas!
On Tue, Oct 31, 2023 at 01:27:22PM +0100, Lucas Nussbaum wrote:
> See this message:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042585;msg=7
> and this comment from Dmitry Shachnev:
> # Dear Maintainers, I am going to upload Sphinx 7.2.6 to unstable next
> we
ns (although
> I may still be able to break them with PYTHONPATH).
I want to add that this concern applies to Sphinx too.
Newer versions of its dependencies (e.g. docutils or jinja2) can easily break
Sphinx. As well as incompatible versions of some Sphinx extensions installed
from PyPI.
er to get up to date version."""
> if version := os.environ.get("DEB_VERSION_UPSTREAM"):
> return version
> # importing self into setup.py is unorthodox, but param has no
> # required dependencies outside of python
>
ers packaged separately. It looks
like it's updated quite frequently (around 2 times a month, see [1]), so
having it as a separate package will allow us to update it on its own
schedule.
--
Dmitry Shachnev
signature.asc
Description: PGP signature
he mean
> time, it is unfortunately my opinion that it's too late for Bookworm and
> that we must keep Nose for one more release.
I forgot to reply here, but I uploaded fixed nose on Tuesday:
https://tracker.debian.org/news/1398350/accepted-nose-137-9-source-into-unstable/
--
Dmitry
t; important) packages from the Debian repo.
There are bugs filed against every package:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?users=python-modules-t...@lists.alioth.debian.org;tag=nose-rm
--
Dmitry Shachnev
signature.asc
Description: PGP signature
On Sun, Aug 21, 2022 at 04:04:36PM +0300, Dmitry Shachnev wrote:
> Hi,
>
> nose [1] is a testing framework for Python, which is dead and unmaintained
> since 2015 [2][3].
>
> The former maintainer of nose recommends projects using nose to switch to
> nose2 [4], pytest [5] or
Hi Samuel!
On Sun, Aug 21, 2022 at 03:11:59PM +0200, Samuel Thibault wrote:
> Hello,
>
> Dmitry Shachnev, le dim. 21 août 2022 16:04:36 +0300, a ecrit:
> > Samuel Thibault
> >dogtail
>
> ? it's using python3-nose2, not python-nose.
debian/tests/c
://docs.nose2.io/en/latest/
[5]: https://docs.pytest.org/en/latest/
[6]: https://docs.python.org/3/library/unittest.html
[7]: https://github.com/pytest-dev/nose2pytest
[8]: https://docs.python.org/3/library/2to3.html#module-lib2to3
--
Dmitry Shachnev
Adrian Vondendriesch
flask-mongoengine (U)
Adrien
ib/python3/dist-packages (without the part).
You can install to /usr/lib/python3.10/dist-packages if you want, then
dh_python3 will move from python3.10 to python3.
--
Dmitry Shachnev
signature.asc
Description: PGP signature
d a patch to make searchtools.js support search indexes from older
Sphinx versions:
https://salsa.debian.org/python-team/packages/sphinx/-/commit/278114b7292a072e
I will upload this a bit later today.
--
Dmitry Shachnev
signature.asc
Description: PGP signature
Hi Thomas!
On Thu, Nov 11, 2021 at 11:04:10AM +0100, Thomas Goirand wrote:
> On 10/24/21 3:24 PM, Dmitry Shachnev wrote:
> > If anyone is still using nose (1.x), please port your packages to nose2,
> > pure unittest or pytest. I am attaching a dd-list and I intend to do a MBF
>
ild.testfiles is taken into account after PYBUILD_BEFORE_TEST?
Yes, before.
--
Dmitry Shachnev
signature.asc
Description: PGP signature
ld.testfiles.
If no, also add this line to debian/rules:
export PYBUILD_BEFORE_TEST={interpreter} setup.py egg_info
Example package where I am doing this is pybtex-docutils.
--
Dmitry Shachnev
signature.asc
Description: PGP signature
er of packages you have depending on nose, but if
they all come from the same upstream, maybe you can convince this upstream
to not rely on dead software.
--
Dmitry Shachnev
signature.asc
Description: PGP signature
er to simply
let nose die (it is abandoned since 2016).
If anyone is still using nose (1.x), please port your packages to nose2,
pure unittest or pytest. I am attaching a dd-list and I intend to do a MBF
in a few weeks when I have more time.
--
Dmitry Shachnev
Adrian Vondendriesch
flask-mongoengin
binary packages to match already existing sphinx
> theme package names?
I would follow the naming policy and use python3-sphinx-press-theme.
--
Dmitry Shachnev
signature.asc
Description: PGP signature
Also you can try to look where PyQt expects the executables to be:
>>> from PyQt5.QtCore import QLibraryInfo
>>> QLibraryInfo.location(QLibraryInfo.LibraryExecutablesPath)
In any case, this command should also help:
export QTWEBENGINEPROCESS_PATH=/usr/lib/x86_64-linux-gnu/qt5/libexec
--
Dmitry Shachnev
signature.asc
Description: PGP signature
;670 | team+pyt...@tracker.debian.org
> (9 rows)
>
> We should fix them all.
Except the first two (which are valid addresses not related to our team).
--
Dmitry Shachnev
signature.asc
Description: PGP signature
ion it earlier): when referring
to files you can also use :file:. The difference is only semantic, I think
it will produce the same result:
https://www.sphinx-doc.org/en/master/usage/restructuredtext/roles.html#role-file
--
Dmitry Shachnev
signature.asc
Description: PGP signature
hinx without content changes.
>
> There's no direct equivalent in RST for
> python3.Y, the best is
> ``python3.Y``.
You can use :samp:`python3.{Y}`. See:
https://www.sphinx-doc.org/en/master/usage/restructuredtext/roles.html#role-samp
--
Dmitry Shachnev
signature.asc
Description: PGP signature
020-September/000860.html
--
Dmitry Shachnev
signature.asc
Description: PGP signature
h):
> dpkg-buildpackage: information: system architecture amd64
> dpkg-source: failure: source package has 2 conflicting values:
> "python-my-package" and "python3-my-package"
You need to change both debian/control and debian/changelog.
--
Dmitry Shachnev
signature.asc
Description: PGP signature
his is only about updating fields in git, there is no need to
upload to archive just because of metadata change.
--
Dmitry Shachnev
signature.asc
Description: PGP signature
cation, not one that redirects.
Probably also update Maintainer/Uploader fields with the new team name/email.
--
Dmitry Shachnev
signature.asc
Description: PGP signature
074.
Upstream promises to make a new release within a week. If you don't mind,
I will wait for that and then upload the new release to Debian.
--
Dmitry Shachnev
signature.asc
Description: PGP signature
to fix this issue
I have just uploaded sphinx 2.4.3-5 where dh_sphinxdoc gained the ability
to symlink language_data.js (for English), so this should be fixed.
--
Dmitry Shachnev
signature.asc
Description: PGP signature
nts to Python 3.
>
> I wonder, what they do, if there will be a Python 4...
AFAIK Python 4 is not planned even in long term (e.g. because that would break
a lot of programs that rely on sys.version_info.major):
https://www.python.org/dev/peps/pep-0602/
--
Dmitry Shachnev
signature.asc
Description: PGP signature
import them, but maybe there is some
benefit in keeping the normal debug versions too?
--
Dmitry Shachnev
signature.asc
Description: PGP signature
Hi Geert!
On Sun, Jul 05, 2020 at 07:05:28PM +0200, Geert Stappers wrote:
> Hi,
>
> Where to find the source of python-policy?
I believe it is here:
https://salsa.debian.org/cpython-team/python3-defaults/-/blob/master/debian/python-policy.dbk
--
Dmitry Shachnev
signature.asc
Descrip
n't happen soon, but I will fix this bug in the next Sphinx 2.4 upload.
--
Dmitry Shachnev
signature.asc
Description: PGP signature
toapi-doc depend on ${sphinxdoc:Depends}.
- Drop Suggests: libjs-jquery, libjs-underscore as they will be in Depends.
--
Dmitry Shachnev
signature.asc
Description: PGP signature
e updates
> > until we're ready to drop them and running tests can still have
> > value), but i think the cost/benefit ratio points towards removing
> > python-pytest soon rather than wait.
> >
> > There are only 25 packages that would need updating, and most
y API and the sooner we start to use it, the better.
One issue that comes to mind: how will we specify the install location in a
way that will work with any backend? In other words, what is the replacement
for distutils' --install-layout=deb?
--
Dmitry Shachnev
signature.asc
Description: PGP signature
/modules.
Can some admin please run it? (You need to get an API token and put a
SALSA_TOKEN=... line to ~/.devscripts first.)
python-team/applications is not affected because it seems to already use KGB.
--
Dmitry Shachnev
salsa.sh
Description: Bourne shell script
signature.asc
Description
ition.
I think it makes sense.
Maybe you can paste the list of 20 affected apps, though?
--
Dmitry Shachnev
signature.asc
Description: PGP signature
o update branch names in debian/gbp.conf accordingly. And gbp should create
a pristine-tar branch when you update to a newer release.
--
Dmitry Shachnev
signature.asc
Description: PGP signature
HONFAULTHANDLER=1.
To get the C stack trace, you need to run the Python interpreter in a debugger
like gdb. Better to do this locally of course, not in the CI.
--
Dmitry Shachnev
signature.asc
Description: PGP signature
tput of the following commands in the Python console:
>>> import pkg_resources
>>> pkg_resources.get_distribution('PyQt5')
For me it prints “PyQt5 5.14.1 (/usr/lib/python3/dist-packages)”.
--
Dmitry Shachnev
signature.asc
Description: PGP signature
bleReleaseUpdates#SRU_Bug_Template
The whole sip 4.19.21 won't be backported, but it is possible to cherry-pick
individual fixes.
--
Dmitry Shachnev
signature.asc
Description: PGP signature
e source of error.
I think pybuild just calls setup.py build and then setup.py install.
So it is a question to upstream build system, why are files recompiled during
install.
--
Dmitry Shachnev
signature.asc
Description: PGP signature
es installed, they must be copied manually (right?).
You can use debian/pybuild.testfiles to copy the test files. See pybuild(1)
for details.
--
Dmitry Shachnev
signature.asc
Description: PGP signature
anning to work on that package next.
Thanks! Feel free to ping me directly about it.
--
Dmitry Shachnev
signature.asc
Description: PGP signature
umentation, or remove that variable and python3-sphinx from
Build-Depends.
Please fix that and I will sponsor this.
Also are you interested in python-traitsui package? It would be nice to get
it ported to Python 3 or removed.
--
Dmitry Shachnev
signature.asc
Description: PGP signature
ted? Like “python-foo-doc is a documentation package has 0 external
rdeps”.
Also, in other lines I would also change “have” to “has”.
--
Dmitry Shachnev
signature.asc
Description: PGP signature
binding exists.
> I'm gonna go thru some of the dependencies and will see if i can
> remove some, in particular now that i've remored the -doc package from
> the git repo, but i'm not gonna get rid the whole unittest suite.
>
> thanks for your work on this, and to n
onder if we can also remove python-matplotlib2-doc and related sphinx
build-dependencies. For developers working on software using matplotlib, the
documentation for its latest version (python-matplotlib-doc) should be enough.
--
Dmitry Shachnev
signature.asc
Description: PGP signature
are overriding dh_installdocs and running it only
for one package.
Either remove the -ppython-opentracing-doc argument, or add another call
with --remaining-packages option.
--
Dmitry Shachnev
signature.asc
Description: PGP signature
I think using one of these two pages will be better:
- https://pypi.org/simple/wurlitzer/
- https://pypi.debian.net/wurlitzer/
--
Dmitry Shachnev
signature.asc
Description: PGP signature
s from upstream branch, and run
pristine-tar commit after generating the new tarball.
--
Dmitry Shachnev
signature.asc
Description: PGP signature
o specify it in
debian/gbp.conf (gbp expects master by default).
There is an attempt to standardize, DEP-14 (which suggests debian/master),
but it is not yet widely adopted:
https://dep-team.pages.debian.net/deps/dep14/
--
Dmitry Shachnev
signature.asc
Description: PGP signature
On Sat, Aug 31, 2019 at 06:57:23PM +0300, Dmitry Shachnev wrote:
> On Sun, Sep 01, 2019 at 12:34:02AM +0900, Norbert Preining wrote:
> > Now, the interesting thing are the error messages. One of them is
> > [...]
> > httperror_seek_wrapper: HTTP Error 403: request dis
:
http_proxy= dh_auto_test -- --system custom --test-args "cd {build_dir};
{interpreter} run_tests.py"
With this command, only three tests are failing for me.
--
Dmitry Shachnev
signature.asc
Description: PGP signature
e in its own directory, and cleaning up after that.
See pybuild(1) for details.
--
Dmitry Shachnev
signature.asc
Description: PGP signature
Hi Andreas,
On Sat, Aug 31, 2019 at 09:57:16AM +0200, Andreas Tille wrote:
> Hi,
>
> I have removed the Python2 package from d/control and all python-*
> Build-Depends in Git[1].
I see that python-all is still present in Build-Depends (line 9).
--
Dmitry Shachnev
signature.asc
Package: ftp.debian.org
Severity: normal
User: debian-python@lists.debian.org
Usertags: py2removal
python-gdata was never ported to Python 3.
Upstream is dead and python3-googleapi may be a better replacement.
The last reverse dependency (ckanclient) was RMed today.
--
Dmitry Shachnev
(#899010).
- Not in testing.
- Deprecated upstream, replaced with ckanapi (#912472).
Reverse dependencies checked with dak rm -Rn ckanclient.
--
Dmitry Shachnev
signature.asc
Description: PGP signature
orry. I will use correct tags next time.
Both mine and Andrey’s existing bugs now show on [1], so it looks like you
(or someone else) already fixed them.
[1]:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?users=debian-python@lists.debian.org;tag=py2removal
--
Dmitry Shachnev
signature.asc
Description: PGP signature
your branch, ready for a rebase...
Nice option, thanks for the suggestion!
So Guðjón, next time if you have already imported a new tarball and do not
have patch-queue/debian/master branch, use this command instead.
--
Dmitry Shachnev
signature.asc
Description: PGP signature
remembered before
> But fixing the patches with quilt before importing them the second
> time seems to fix all my problems.
If it does not break the patches metadata then it also works.
--
Dmitry Shachnev
signature.asc
Description: PGP signature
/ignatenkobrain/sphinxcontrib-issuetracker/pull/13
--
Dmitry Shachnev
signature.asc
Description: PGP signature
ld in debian/copyright, then change second line to this:
opts=dversionmangle=s/\+dfsg//,repacksuffix=+dfsg \
--
Dmitry Shachnev
signature.asc
Description: PGP signature
developing ghini [2] instead, which has similar
purpose. If someone is interested, it is better to package that instead.
[1]: https://github.com/Bauble/bauble.classic
[2]: https://github.com/Ghini/ghini.desktop
--
Dmitry Shachnev
signature.asc
Description: PGP signature
upstream is alive [1] and upstream version is ported
to Python 3 and Qt 5, so this package can be reintroduced if someone wants
to work on it.
Reverse dependencies checked with dak rm -Rn opensesame.
[1]: https://github.com/smathot/OpenSesame
--
Dmitry Shachnev
signature.asc
Description: PGP
among other alternatives.
E.g. stardict-czech has
Recommends: sdcv (>= 0.4.2-2) | stardict (>= 2.4.6) | stardict-gtk (>= 2.4.6) |
goldendict | qstardict | babiloo | dictionarystar
--
Dmitry Shachnev
signature.asc
Description: PGP signature
lper-compat (= 10),
debhelper-compat (= 11), debhelper-compat (= 12).
So this change is safe to do for packages whose compat level is ≥ 9.
--
Dmitry Shachnev
signature.asc
Description: PGP signature
On Thu, Mar 21, 2019 at 02:36:01PM +0300, Dmitry Shachnev wrote:
> Hi Marie!
Perhaps this should have been ‘Hi Alexandre’. Sorry if I got this wrong.
--
Dmitry Shachnev
signature.asc
Description: PGP signature
the files produced by Sphinx will have the right path, and there
won’t be any need for making symlinks.
--
Dmitry Shachnev
(maintainer of both sphinx and mathjax packages)
signature.asc
Description: PGP signature
this team
I hope you will be added to the team, but while you are not, why can’t
you just use merge requests?
--
Dmitry Shachnev
signature.asc
Description: PGP signature
e to fix this,
but if he does not respond, I will merge it with my suggestion applied.
(I hope Ondřej does not mind.)
--
Dmitry Shachnev
signature.asc
Description: PGP signature
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 re
d 10-day migration
> period, would anyone be kind enough to review and upload this new
> release today?
Uploaded.
--
Dmitry Shachnev
signature.asc
Description: PGP signature
e last command won’t do anything though, since the upstream tag
already exists, and you have not created a Debian release/tag yet.
--
Dmitry Shachnev
signature.asc
Description: PGP signature
revert HEAD
The last commits in upstream and pristine-tar branches look fine, no
need to revert them.
Just revert the last commit in debian/master (as you did above), then
merge upstream/0.3.8 tag into debian/master and update the changelog.
It should be enough.
--
Dmitry Shachnev
signature.asc
Description: PGP signature
ous command
left you). If you run ‘git checkout debian/master’ before ‘gbp import-orig’
this might work even with older git-buildpackage versions.
I recommend setting up your shell prompt to show the current branch, it will
make it easier to understand what is going on. You can find some instruction
. I think that
at least specifying debian-branch is definitely needed. If you want I can
simplify it to just that one line before merging, and/or link to the wiki
instead of recommending any specific gbp.conf content.
--
Dmitry Shachnev
signature.asc
Description: PGP signature
rsions --supported and make the autopkgtest depend on
python3-all.
--
Dmitry Shachnev
signature.asc
Description: PGP signature
s/-/group_members?search=Stappers
https://salsa.debian.org/groups/python-team/applications/-/group_members?search=Stappers
I hope Ondřej or another admin can correct it.
--
Dmitry Shachnev
signature.asc
Description: PGP signature
yourself,
which is not needed since all PAPT repos were migrated automatically.
(Of course your request to join the team is still valid.)
--
Dmitry Shachnev
signature.asc
Description: PGP signature
, but everything else is quite generic.
--
Dmitry Shachnev
signature.asc
Description: PGP signature
t ends
> up with an empty python3-edlib package despite the file
>
>
> $(CURDIR)/.pybuild/cpython3_3.6_edlib/build/edlib.cpython-36m-x86_64-linux-gnu.so
>
> is created. Am I missing something in the final install step?
The attached patch shou
rtbug ftp.debian.org”, then select
NBS as request type and follow the instructions.
--
Dmitry Shachnev
signature.asc
Description: PGP signature
ent, this needs to be
handled manually.
In your case 2to3 produces different output in 3.6 and 3.7. The resulting
code is still identical, so you can safely remove the differing files.
I used this override in a similar case:
https://salsa.debian.org/python-team/modules/pygithub/blob/master/debian/
n use for documenting
Python code, and that code is Python 2 only.
Also there may be custom Sphinx extensions written in Python 2.
--
Dmitry Shachnev
signature.asc
Description: PGP signature
1 - 100 of 287 matches
Mail list logo
