Le 5/30/21 à 4:31 PM, Guido van Rossum a écrit :
> What are you trying to get from the archives? It is *possible* that I
> have a personal archive saved somewhere.
I'm not even sure I remember my initial question... But it could be:
> is the fact some things (like generators) give iterators inst
Le 5/29/21 à 11:14 PM, Guido van Rossum a écrit :
> It looks like what's left of the archives is largely spam?
Yes.
SourceForge staff has manually hidden most spam on this list a few days
ago to help see better, but the interesting discussion is no longer here.
They checked in the mbox file on d
Some bad news about python-iterat...@lists.sourceforge.net, looks like
sourceforge lost a huge part of the mailing list: they have 0 message
before Sep. 2001.
So I think I'll soon drop the link(s) refering to it in the PEPs.
--
[Julien Palard](https://mdk.fr)
Hi,
Le 5/25/21 à 9:18 PM, Brett Cannon a écrit :
> Is there something to do here? The python-iterators mailing list is
> already marked as public.
Looks like Guido is faster than you and set it public already. But looks
like the archives are corrupted or something, it's almost empty.
I sent a ma
Le 5/11/21 à 8:39 PM, Guido van Rossum a écrit :
> I doubt that anyone has the keys to the python project on sourceforge
> any more... :-( We've abandoned that platform nearly two decades ago.
That's right…
Sourceforge staff mentionned there's the list of current admins here:
=> https://sourcefo
Hi,
PEP 234 mention
https://sourceforge.net/p/python/mailman/python-iterators/ but the
project mailing list archives are marked as "hidden".
Looks like projects admin and developers can get the "hidden link", but
I think it would be nice to "unhide" the archives if someone is still
admin there an
Thanks everyone for the feedback.
I think the best way to handle this is to make the three next releases
(3.10, 3.11, 3.12) Sphinx 2 and Sphinx 3 compatible, this would gather
requiered benefits:
- Ease of backporting: from any dev version we can backport
documentation changes to the previous
Hi Matthias,
Le 2021-01-13 à 12:27, Matthias Klose a écrit :
> That's not true. Ubuntu 20.04 LTS still sees updates to subminor Python 3.8
> versions, having sphinx 1.8.5.
I do agree to *not* bump our Sphinx dependencies for already published
Pythons.
Would it be OK to bump Sphinx to 3.2 for Py
Le 2021-01-13 à 00:28, Victor Stinner a écrit :
> Since documentation changes are backported to 3.8 and 3.9 stable
> branches, if we increase the minimum required Sphinx version in
> master, I would prefer to also increase it in 3.8 and 3.9 branches.
Bumping a dependency on the next release is alr
Le 2021-01-13 à 00:09, Senthil Kumaran a écrit :
> Wouldn't this a bug with Sphinx?
No, this is a documented breaking change between Sphinx 2 and Sphinx 3.
> Why would that be special cased with a flag (strip_signature_backslash)?
The strip_signature_backslash has been introduced to allow Sphinx
During the development of cpython 3.10, Sphinx was bumped to 3.2.1.
Problem is Sphinx 3 have some incompatibilities with Sphinx 2, some that
we could work around, some are bit harder, so we may need to bump
`needs_sphinx = '3.2'` (currently it is 1.8).
I found two incompatibilities:
- We're us
Hi Christian,
> the table with auditing events does not render on docs.python.org,
> https://docs.python.org/3.9/library/audit_events.html. Steve and I are
> going to present the auditing feature tomorrow at EuroPython. It would
> be helpful to have the table available.
This was not an easy one..
> I can trivially attach the built docs as a ZIP file to the Azure
> Pipelines build, though that doesn't help the "preview on my phone"
So one can build an HTTP server that gathers doc builds from Azure and expose
them?
--
Julien Palard
https://mdk.fr
_
Considering feedback from Ned, what about building this as an independent
service? We don't really need to interface with python.org at all, we just need
some hardware, a domain, some code to interface with github API and... to start
it's probably enough? It would be a usefull POC.
--
Julien P
Hi,
[Larry]
> 3.5 also got some doc-only changes related to the online "version switcher"
> dropdown.
About this I have a question: the switchers for english version of 3.4 and 3.5
are disabled (https://docs.python.org/3.5/) but not disabled for translations
(https://docs.python.org/fr/3.5/).
Hi Brett,
On Wed, 29 Mar 2017 at 13:13 Julien Palard wrote:
What kind of support does Read the Docs have for translations? I have no active
plans to push for this but it has been idea in the back of my head for a while
so it would be good to know if such a move would make this easier or harder
Hi, little follow-up about this PEP.
Please check with the PSF that this is what we really want. In the past the
suggestion has been to **not** use the PSF license with all of its historical
baggage but instead use something like Apache. But since IANAL we really should
ask the PSF what the bes
Hi Jakub,
Typos
Fixed, thanks.
* Julien Palard , 2017-03-29, 07:47:
>It's redundant to display both language and country code if they're the same,
>for example: "de-DE" or "fr-FR".
This wording is unfortunate. It seems to imply that you can meaningfully
compare a language code and a territory c
Hi Brett, thanks for the feedback!
Please check with the PSF that this is what we really want.
Gladly, but … how? I'm very new to all those process and have now idea on how I
can get in touch with PSF lawyers.
What kind of support does Read the Docs have for translations? I have no active
plan
Hi.
Here's PEP 545, ready to be reviewed!
This is the follow-up to the "PEP: Python Documentation Translations" thread on
python-ideas [1]_,
itself a follow-up of the "Translated Python documentation" thread on
python-dev [2]_.
This PEP describes the steps to make existing and future translatio
20 matches
Mail list logo
