Change by Julien Palard :
--
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.or
New submission from Julien Palard :
According to [1] there's no concensus on which minimum Sphinx version we should
use for Python 3.10.
"sadly" since https://github.com/python/cpython/pull/23620 which make use of a
Sphinx 3.2.0 only feature, we should bump it to 3.2, but it m
Change by Julien Palard :
--
keywords: +patch
pull_requests: +22971
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/24142
___
Python tracker
<https://bugs.python.org/issu
Julien Palard added the comment:
In favor of Sphinx 3 only :
- We have :no-trim-doctest-flags: which fixes https://bugs.python.org/issue36675
- backslash handing is different in Sphinx 2 and Sphinx 3:
https://bugs.python.org/issue42822
In favor of keeping compatibility with Sphinx 2
New submission from Julien Palard :
Running `python3 -m pydoc ensurepip` gives me:
https://docs.python.org/3.9/library/ensurepip
but it should be:
https://docs.python.org/3.9/library/ensurepip.html
Issue is in getdocloc function on the line:
docloc = "%s/%s" % (doc
Change by Julien Palard :
--
keywords: +patch
pull_requests: +23001
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/24174
___
Python tracker
<https://bugs.python.org/issu
Julien Palard added the comment:
This is now fixed on the docs server thanks to [1], so it should work for
already release Python 3.9 :)
[1]: https://github.com/python/psf-salt/pull/198
I still did a PR on cpython to avoid a redirection, and get cpython itself out
of the "people use
Julien Palard added the comment:
Question: Why do we keep setuptools?
According to PEP453:
> Once pip is able to run pip install --upgrade pip without needing setuptools
> installed first, then the private copy of setuptools will be removed from
> ensurepip in subsequent CPython
Change by Julien Palard :
--
pull_requests: +23103
pull_request: https://github.com/python/cpython/pull/24282
___
Python tracker
<https://bugs.python.org/issue42
Julien Palard added the comment:
Nice find! I am able to reproduce it too in many Python releases.
I see differnt ways we can fix it:
# Using a random secret generated at startup time
Used any way, like by providing an hmac on getfile urls to ensure they are
signed with the server secret
Julien Palard added the comment:
New changeset 5c1f15b4b1024cbf0acc85832f0c623d1a4605fd by Julien Palard in
branch 'master':
bpo-42843: Keep Sphinx 1.8 and Sphinx 2 compatibility (GH-24282)
https://github.com/python/cpython/commit/5c1f15b4b1024cbf0acc85832f0c62
Change by Julien Palard :
--
resolution: -> not a bug
stage: patch review -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.or
Julien Palard added the comment:
Due to https://github.com/python/cpython/pull/24282 this is sadly un-fixed.
Either we find another way to fix this, either we wait 3 releases and we
re-commit https://github.com/python/cpython/pull/23620.
--
resolution: fixed -> later
stage: resol
Julien Palard added the comment:
New changeset eb9983c59b0683270328b5c40a115bb028209511 by Julien Palard in
branch 'master':
bpo-42869: Avoid an HTTP redirection. (GH-24174)
https://github.com/python/cpython/commit/eb9983c59b0683270328b5c40a115b
Change by Julien Palard :
--
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.or
Julien Palard added the comment:
I can reproduce it in 3.10 too.
--
versions: +Python 3.10
___
Python tracker
<https://bugs.python.org/issue43136>
___
___
Pytho
Julien Palard added the comment:
I'm +1 on adding ** to match.
My first bet would be to add it to match, not adding a new method, nor a flag,
as it should not break compatibility:
It would only break iif someone have a `**` in a match AND does *not* expect it
to be recursive (as it
New submission from Julien Palard :
Currently we can't build the doc using sphinx parallel builds, like:
`sphinx-build -j auto`, because the audit-events table [1] is not generated in
this case.
[1]: https://docs.python.org/3/library/audit_events.html
To reproduce:
make -
Julien Palard added the comment:
New changeset 735d902b363b759df9ff00e58bbf4f7e2bde78cd by Florian Dahlitz in
branch 'master':
bpo-40798: Generate a different message for already removed elements (GH-20483)
https://github.com/python/cpython/commit/735d902b363b759df9ff00e58bbf4f
Change by Julien Palard :
--
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.or
Julien Palard added the comment:
Thanks @Rémi for this great idea and Florian for the implementation!
--
___
Python tracker
<https://bugs.python.org/issue40
New submission from Julien Palard :
This is to track [1] from the cpython point of view, mostly just to remove the
switchers as they are now handled by docsbuild-scripts.
see: https://mail.python.org/pipermail/doc-sig/2020-June/004200.html
[1]: https://github.com/python/docsbuild-scripts
Change by Julien Palard :
--
keywords: +patch
pull_requests: +20147
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/20969
___
Python tracker
<https://bugs.python.org/issu
Julien Palard added the comment:
In production, this is now starting to fix links and picker for the 2.7
version, which was stating:
Docs by version
Python 3.9 (in development)
and now displays:
Docs by version
Python 3.10 (in development
Change by Julien Palard :
--
keywords: +patch
pull_requests: +20389
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/21237
___
Python tracker
<https://bugs.python.org/issu
Change by Julien Palard :
--
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.or
Julien Palard added the comment:
New changeset a103e73ce8d34e3af5f556ee9090ce89249d565e by Julien Palard in
branch 'master':
bpo-40742: Doc: fix parallel build. (GH-21237)
https://github.com/python/cpython/commit/a103e73ce8d34e3af5f556ee9090ce
Change by Julien Palard :
--
pull_requests: +20558
pull_request: https://github.com/python/cpython/pull/21409
___
Python tracker
<https://bugs.python.org/issue12
Julien Palard added the comment:
Strange fact, this was already fixed in
011525ee92eb1c13ad1a62d28725a840e28f8160 (which closes issue10761, nice spot
Andrew) but was lost during a merge in 0d28a61d23:
$ git show 0d28a61d23
commit 0d28a61d233c02c458c8b4a25613be2f4979331e
Merge: ed3a303548
New submission from Julien Palard :
When running the following command from the Doc/ directory:
./venv/bin/sphinx-build -Q -b gettext -D gettext_compact=0 . ../pot/
everything goes right, but when running the following from cpython direcory:
./Doc/venv/bin/sphinx-build -Q -b gettext
Change by Julien Palard :
--
keywords: +patch
pull_requests: +20665
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/21529
___
Python tracker
<https://bugs.python.org/issu
Change by Julien Palard :
--
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.or
Julien Palard added the comment:
Hi Simon, thanks for reporting!
This looks like a Google issue, not a Python documentation issue: Google tries
to deduce something better than the URL to display to the user, and fails,
please open the issue on the Google bug tracker instead.
(As a side
New submission from Julien Palard :
As reported by Graham Ewart on docs@,
in https://docs.python.org/3/library/stdtypes.html#common-sequence-operations:
s * n or n * s | equivalent to adding s to itself n times
is badly worded. In fact it's more like n-1 times, but yet it's not a
New submission from Julien Palard :
Currently it looks like our `textwrap.fill` implementation does not conforms to
the Unicode Line Breaking Algorithm from the unicode standard.
Should this be enhanced?
If so, as a sidenote, it could be nice to have the override parameter of
libunistring
Julien Palard added the comment:
Could be "related" to https://bugs.python.org/issue41975.
--
nosy: +mdk
___
Python tracker
<https://bugs.python.o
Julien Palard added the comment:
Thanks for the heads up cocoatomo!!
Fixed:
https://github.com/python/docsbuild-scripts/commit/c23b401425a47b9c8eaa9626701ba6b9b50531f7
--
resolution: -> fixed
stage: patch review -> resolved
status: open -&g
New submission from Julien Palard :
I was not here 21 years ago when it was introduced [1], but according to the
commit message it was introduced to find leftover Latex mardown.
It tries to find 4 patterns in Sphinx node text (not in raw rst files):
::(?=[^=])|# two :: (but NOT
Julien Palard added the comment:
New changeset ee2549c2ba8bae00f2b2fea8a39c6dfbd1d06520 by Julien Palard in
branch 'master':
bpo-41028: Doc: Move switchers to docsbuild-scripts. (GH-20969)
https://github.com/python/cpython/commit/ee2549c2ba8bae00f2b2fea8a39c6d
Julien Palard added the comment:
Hi!
Thanks Alex for reporting, and everyone involved.
This has been fixed in python-docs-theme, so it's fixed for >=3.8. As 3.7 is in
security-only (and embeds python-docs-theme), better not touch it.
Bests.
--
resolution: -> fixed
s
Julien Palard added the comment:
Good idea Ned!
So proposed plan:
- Drop it from docs build and the CI to avoid time loss.
- Add it as a step of PEP 101, for a few release, for good measures
- I'll check it from time to time between releases, just to ensure it does not
accumulate to
Change by Julien Palard :
--
keywords: +patch
pull_requests: +22204
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/23313
___
Python tracker
<https://bugs.python.org/issu
Julien Palard added the comment:
New changeset c9c6e9f89aa68ce8094393a1a5575b67d26bc8c8 by Julien Palard in
branch 'master':
bpo-42238: Doc: Remove make suspicious from the CI and docs builds. (GH-23313)
https://github.com/python/cpython/commit/c9c6e9f89aa68ce8094393a1a5575b
Julien Palard added the comment:
New changeset 4fedd7123eaf147edd55eabbbd72e0bcc8368e47 by Julien Palard in
branch 'master':
bpo-12800: tarfile: Restore fix from 011525ee9 (GH-21409)
https://github.com/python/cpython/commit/4fedd7123eaf147edd55eabbbd72e0
Julien Palard added the comment:
I think I can backport it to 3.7, and I let you choose if 2.7 need this.
--
___
Python tracker
<https://bugs.python.org/issue28
Julien Palard added the comment:
FWIW here's my feedback (as a Python teacher and doc guy):
I find that newcomers are good to ignore what they don't understand, so a
newcomer exposed to "foo(a, b, /)" will no run away nor cry, he will just
ignore the slash and understand
Change by Julien Palard :
--
pull_requests: +13952
pull_request: https://github.com/python/cpython/pull/13168
___
Python tracker
<https://bugs.python.org/issue31
New submission from Julien Palard :
In Doc/faq/design.rst there's "with an eye to making it easily tested.".
I'm not native english, but I think "making" is wrong here, maybe "make"?
--
assignee: docs@python
components: Documentation
keywords:
New submission from Julien Palard :
In Doc/library/parser.rst I can read:
The parse trees are not typically compatible from one version to another,
whereas source code has always been forward-compatible.
But I don't think this is right, I think of print for example.
Maybe just r
New submission from Julien Palard :
The following commit:
44f91c388a6f4da9ed3300df32ca290b8aa104ea
bpo-37390: Add audit event table to documentations (GH-14406)
Also updates some (unreleased) event names to be consistent with the others.
breaks PDF builds.
Reproductible using
Julien Palard added the comment:
Looks like a failure during library.pdf, from why we try to link to c-api.
In the sphinx latex builder:
if docname not in self.docnames:
raise NoUri
in self.docnames during the library build, we're only having library/* links.
So c-api/co
New submission from Julien Palard:
A language switch, like the actual version switch, should allow to change from
a translation to another.
I mean jumping from docs.python.org/3/ to docs.python.org/fr/3/ and so on.
It's already discussed in PEP 545.
--
messages: 299234
nosy
Julien Palard added the comment:
@terry About Japanese translation, Inada Naoki is the coordinator, their
repository is created (https://github.com/python/python-docs-ja) they just have
to push now.
Once this language switch fully tested / implemented / released, it will be
easy to add a
Julien Palard added the comment:
I added blurb to the docs build script
(https://github.com/python/docsbuild-scripts/commit/06375b6d74f6d5613fcd48030b3af8032854c87d),
so 3.5 should build soon. The requirements looks automatically pulled from
psf-salt https://github.com/python/psf-salt/blob
Julien Palard added the comment:
Still unfixed on docs.iad1.psf.io, the venv I modified is only used for sphinx
and uses Python 2. If we can easily upgrade it to Python 3 we'll be able to
pass it as the PYTHON parameter for make in docsbuild-script, allowing blurb to
be found.
see:
Julien Palard added the comment:
We upgraded Python on docs.python.org to 3.6 (from 3.4), so blurb can run. I
pushed https://github.com/python/docsbuild-scripts/pull/22 to give the right
Python in the PYTHON Makefile parameter. I'm currently running a test build
locally and will merge
New submission from Julien Palard:
As, by default, "english" is selected, and as we're building translations far
before rendering them public by adding them to the language switcher, there's a
timespan where a human can voluntarily land on a translation with a language
New submission from Julien Palard:
Japanese translation have reached the prerequisites from PEP 545, their last
step is to be added to the language switcher.
Current build has been reviewed by Inada and is OK:
https://docs.python.org/ja/3.7/
Note: On the current build, the /ja/ is not
New submission from Julien Palard:
Since ja has been added to the language switch, a bug appeared and in some case
the switch won't ... switch.
Due to a regex bug in switchers.js, a needed trailing slash is sometimes not
matched. It has not been detected previously as it can happen only
Changes by Julien Palard :
--
stage: -> resolved
status: open -> closed
___
Python tracker
<http://bugs.python.org/issue31149>
___
___
Python-bugs-list
Changes by Julien Palard :
--
stage: patch review -> resolved
status: open -> closed
___
Python tracker
<http://bugs.python.org/issue31045>
___
___
Pyth
Julien Palard added the comment:
Now works in 3.7, needs backports to 3.6 and 2.7.
--
___
Python tracker
<http://bugs.python.org/issue31159>
___
___
Python-bug
Julien Palard added the comment:
Arfrever: nice catch!
Inda: What do you think? Any preference between "日本語", "Japanese", and "日本語
(Japanese)"?
I personally don't like much the "日本語 (Japanese)" version, but I don't care
much between "Fr
Julien Palard added the comment:
Are you sure you build is failing? It looks like it succeeded, if we only speak
about the build.
You're seeing AddressSanitizer reports because, during the build, the built
python is used. Like in `./python -E -S -m sysconfig --generate-posix-vars`.
So i
Julien Palard added the comment:
Some (most?) of them looks to be unicode strings, and according to the very end
of the main function:
#ifdef __INSURE__
/* Insure++ is a memory analysis tool that aids in discovering
* memory leaks and other memory problems. On Python exit, the
Julien Palard added the comment:
Segfault occur in Include/object.h line 1054:
#define Py_TRASHCAN_SAFE_BEGIN(op) \
do { \
PyThreadState *_tstate = PyThreadState_GET(); \
if (_tstate->trash_delete_nesting < PyTrash_UNWIND_LEVEL) { \
⧺_tstate->trash_delet
Julien Palard added the comment:
@inada make sense, so I'll change "Français" for "French" for consistency.
--
___
Python tracker
<http:
Julien Palard added the comment:
Has been merged on master, backported to 3.6 and 2.7.
It starts to appear on some versions as the script is currently running, like
in https://docs.python.org/2.7/.
I'll close when I'll see this on al
New submission from Julien Palard:
Since the docsbuild-scripts [1] upgraded its sphinx-build [2], we're having
this error when building the docs:
! Undefined control sequence.
\py@authoraddress -> \strong
{Python Software Foundation}\\ Email: \email {d...
Changes by Julien Palard :
--
status: open -> closed
___
Python tracker
<https://bugs.python.org/issue31149>
___
___
Python-bugs-list mailing list
Unsubscrib
Changes by Julien Palard :
--
stage: -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.org/issue31159>
___
___
Python-bugs-list
Julien Palard added the comment:
Hi Raymond,
I agree, there exist other means of teaching half closed range, but I was more
concerned by self-taught students, alone facing the current range repr than
students well accompanied.
I also agree, let's not change the current repr (for bac
Change by Julien Palard :
--
keywords: +patch
pull_requests: +9847
stage: -> patch review
___
Python tracker
<https://bugs.python.org/issue35221>
___
___
Py
Julien Palard added the comment:
New changeset 6b73bb523a176123a819e4ebac3727d31d861515 by Julien Palard in
branch 'master':
bpo-31146: Don't fallback switcher to english on not-yet pusblished languages.
(GH-10558)
https://github.com/python
Julien Palard added the comment:
Hi Raymond,
I'm mentionning I've spotted the issue in my class just to say "it happen that
newcomers don't get it, I've seen it". As I've seen it I want to fix it. I
don't want to fix it only in my course (it does no
Julien Palard added the comment:
New changeset 361e8683e7340c600b22f4a514b81448ccec66dc by Julien Palard
(Zhiming Wang) in branch 'master':
bpo-35035: Rename email.utils documentation to email.utils.rst (GH-10023)
https://github.com/python/cpyt
Julien Palard added the comment:
New changeset 27c16e33b1acac55641a27faa5a11508ee605adc by Julien Palard (Miss
Islington (bot)) in branch '3.6':
bpo-35035: Rename email.utils documentation to email.utils.rst (GH-10023)
https://github.com/python/cpyt
Julien Palard added the comment:
New changeset 3b7258a5a5fddc6c46f71a89b7c8ce89f4b79641 by Julien Palard (Miss
Islington (bot)) in branch '3.7':
[3.7] bpo-35035: Rename email.utils documentation to email.utils.rst (GH-10023)
https://github.com/python/cpyt
Change by Julien Palard :
--
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.or
Change by Julien Palard :
--
pull_requests: +9920
___
Python tracker
<https://bugs.python.org/issue35035>
___
___
Python-bugs-list mailing list
Unsubscribe:
Julien Palard added the comment:
Currently [1] there's no concensus about:
- Is this a documentation issue and we should document the optimisation?
- Is the optimisation over-zealeous?
[1]: https://mail.python.org/pipermail/python-ideas/2018-October/054342.html
--
nosy:
Change by Julien Palard :
--
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.or
Change by Julien Palard :
--
stage: resolved -> patch review
___
Python tracker
<https://bugs.python.org/issue35035>
___
___
Python-bugs-list mailing list
Un
Change by Julien Palard :
--
pull_requests: +9972
___
Python tracker
<https://bugs.python.org/issue35255>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Julien Palard :
--
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.or
Change by Julien Palard :
--
pull_requests: +9973
___
Python tracker
<https://bugs.python.org/issue35255>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Julien Palard :
--
stage: patch review -> resolved
___
Python tracker
<https://bugs.python.org/issue35035>
___
___
Python-bugs-list mailing list
Un
Julien Palard added the comment:
> I expect that the only thing we could do is put a prominent note at the top
> of each page "This is an unsupported version of the docs, for the latest
> version see blah blah blah" and link to the most recent version.
I'm +1 on th
Julien Palard added the comment:
> Without spending too much time on it, it seems to me there are s number of
> issues here:
> 1. What URL schemes do we have and want to continue to support?
> 2. What things do we want to show up in search engine results?
> 3. How do we make t
Julien Palard added the comment:
Hi Matthias,
Sorry to hear it's a pain for you. Can you explain in more details what hurt
your workflow?
We bumped Sphinx, as Victor said, to fix rendering issues in those
documentation translations: zh-tw, zh-cn, fr and ja, so it's not a feat
Julien Palard added the comment:
Hi Matthias,
I agree that for the smartquotes issue the 1.6.6 should be enough. But we had
multiple small issues fixed in some versions of Sphinx. But mostly for
translation and I don't think you're building the translations?
Also the needs_sphi
Change by Julien Palard :
--
keywords: +patch
pull_requests: +10432
stage: -> patch review
___
Python tracker
<https://bugs.python.org/issue35472>
___
___
Py
Change by Julien Palard :
--
title: python 3.7.2 rc1 bumped the build requirements for no reason -> python
3.7.2 rc1 bumped sphinx requirements a bit too much
___
Python tracker
<https://bugs.python.org/issu
Julien Palard added the comment:
New changeset a9ed8fcdbaeccdb82593525b170fb0544202eeda by Julien Palard in
branch '3.7':
bpo-35472: Doc: For Python 3.7 Sphinx 1.6.6 is enough. (GH-11192)
https://github.com/python/cpython/commit/a9ed8fcdbaeccdb82593525b170fb0
Julien Palard added the comment:
Matthias, I downgraded the needs_sphinx to 1.6.6, as it does not disallow me to
use an up-to-date sphinx in the doc server I'm ok with this.
Hope it helps.
--
resolution: -> fixed
stage: patch review -> resolved
status: ope
Julien Palard added the comment:
New changeset fc8284e22074af8154e9865c8391b955f13a308b by Julien Palard
(Jean-François B) in branch 'master':
bpo-35564: add master_doc='contents' to conf.py (GH-11290)
https://github.com/python/cpython/commit/fc8284e22074af8154e9
Change by Julien Palard :
--
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.or
Julien Palard added the comment:
Looks like you can (no one objected to it).
--
___
Python tracker
<https://bugs.python.org/issue35579>
___
___
Python-bug
New submission from Julien Palard :
In howto/regex.rst I read:
> '^' outside a character class will simply match the '^' character.
Which looks wrong, '^' is the "begin anchor", it's a metacharacter that
typically won't match '^'
Julien Palard added the comment:
The patch (try/except) to make
https://github.com/python/cpython/pull/11251/files work with what Doc/conf.py
says about minimum sphinx version (1.2) is OK for me.
No need to apply it on 3.7 which needs_sphinx 1.6.6 according to its
Doc/conf.py
201 - 300 of 685 matches
Mail list logo
