out.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
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/8e730ae303ae686705ea12f44ef11da926a87cf5
> 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 Shachnev
orted:
- 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
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 nex
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
>
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
an
> 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 Shachnev
nt) 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/contro
://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
-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
>
/pybuild.testfiles is taken into account after PYBUILD_BEFORE_TEST?
Yes, before.
--
Dmitry Shachnev
signature.asc
Description: PGP signature
es.
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
ing 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
o 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
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
nx 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
ber/000860.html
--
Dmitry Shachnev
signature.asc
Description: PGP signature
gt; 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
course this 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
n, not one that redirects.
Probably also update Maintainer/Uploader fields with the new team name/email.
--
Dmitry Shachnev
signature.asc
Description: PGP signature
ream 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
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
ates
> > 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 of them
&g
tart 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
I think it makes sense.
Maybe you can paste the list of 20 affected apps, though?
--
Dmitry Shachnev
signature.asc
Description: PGP signature
ranch 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
e 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
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
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
ing 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 nudge me into looking
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
ases.
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
files 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
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
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
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
> 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
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
, but it is 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
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
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
is 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
Wei) some time 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 request
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
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
bian/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 instructions
how to do it in /usr/lib/git-core/git-sh-prompt.
. 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
ions --supported and make the autopkgtest depend on
python3-all.
--
Dmitry Shachnev
signature.asc
Description: PGP signature
ers
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
eded 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
everything else is quite generic.
--
Dmitry Shachnev
signature.asc
Description: PGP signature
; 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 should fix the
n “reportbug ftp.debian.org”, then select
NBS as request type and follow the instructions.
--
Dmitry Shachnev
signature.asc
Description: PGP signature
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/rules
is in 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
ng, but with the current 314
python-sphinx reverse build-depends it is clear that I will have to ship
sphinx-python2 for quite some time.
--
Dmitry Shachnev
signature.asc
Description: PGP signature
of sphinx (e.g. backports) *and* with installed python-sphinx.
> * should we change sphinx-build to be Python3 only? (and broke current
> packages build with Python2 Sphinx)
I would like to do this in the future, but currently there will be too
many broken packages:
https://lintian.debian
he most popular operations you would need to do.
--
Dmitry Shachnev
signature.asc
Description: PGP signature
/debian-devel-announce/2017/08/msg00006.html.
--
Dmitry Shachnev
signature.asc
Description: PGP signature
ests under Xvfb.
I forked your repository and added QT_DEBUG_PLUGINS=1 before the failing
command. Looks like the process is running out of memory:
https://salsa.debian.org/mitya57/veusz/-/jobs/31240
I do not know what to do with this, but at least we now know the reason.
--
Dmitry Shachnev
On Wed, Jul 04, 2018 at 09:50:51PM -0300, eamanu15 wrote:
> Hello Dmitry,
>
> I just pushed the update the package to Salsa. I pushed the PyGithub_1.40
> version.
Thanks! Uploaded after fixing debian/changelog.
--
Dmitry Shachnev
signature.asc
Description: PGP signature
ed to do it after dh_python3 runs.
So better use this:
override_dh_python3:
dh_python3
rm -rfv debian/python3-github/usr/lib/python3.*
--
Dmitry Shachnev
signature.asc
Description: PGP signature
pload, isn't?
Yes, it is better to merge these entries and keep one entry per actual
upload to archive.
--
Dmitry Shachnev
signature.asc
Description: PGP signature
://alioth-archive.debian.org/git/users/kaction-guest/pygithub.git.tar.xz
[2]: https://wiki.debian.org/Python/GitPackagingPQ
[3]: https://pypi.org/project/PyGithub/1.40/
[4]: https://pypi.debian.net/PyGithub/watch
--
Dmitry Shachnev
signature.asc
Description: PGP signature
” and “python3 -m sphinx” instead of sphinx-build.
--
Dmitry Shachnev
signature.asc
Description: PGP signature
stutils need to be
> updated?
Looks like it has a build-dep loop:
https://buildd.debian.org/status/package.php?p=python3-stdlib-extensions
--
Dmitry Shachnev
signature.asc
Description: PGP signature
right decision, as these reasons still apply.
--
Dmitry Shachnev
signature.asc
Description: PGP signature
in upstream Git but
not in the released tarball:
https://github.com/sphinx-contrib/autoprogram/blob/master/doc/cli.py
Try either adding this file using a patch, or using a tarball from Github
rather than from PyPI.
--
Dmitry Shachnev
signature.asc
Description: PGP signature
1 - 100 of 252 matches
Mail list logo
