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
On 28 March 2017 at 17:31, Nathaniel Smith wrote:
> IMO this is a bug, and depending on how many packages are affected it might
> even call for an emergency 3.6.2. The worst case is that we start getting
> large numbers of packages uploaded to pypi that claim to be 3.6.0 compatible
> but that cras
On Tue, 28 Mar 2017 at 23:36 INADA Naoki wrote:
> On Tue, Mar 28, 2017 at 11:07 PM, Ned Deily wrote:
> > On Mar 28, 2017, at 08:49, INADA Naoki wrote:
> >> Currently, changelog of Python 3.7a1 [1] contains changes between
> >> 3.6b1 and 3.7a1.
> >> So lot's of bugfixes are listed twice or more
Sounds good overall! I only have one thing to suggest in regards to the
license, two grammar tweaks, and a question.
On Wed, 29 Mar 2017 at 08:10 Julien Palard via Python-Dev <
python-dev@python.org> wrote:
> [SNIP]
> Sources of translated documentation will be hosted in the Python
> organization
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
Typos:
english -> English
Febrary -> February
insted -> instead
redundent -> redundant
* 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 ca
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
On 29 March 2017 at 00:40, Terry Reedy wrote:
> [. . .] Eryk Sun suggested a patch for Windows, (and
> the possibility of using pthread_kill). Can you possibly do one for *nix?
> This is out of my ballpark, but the bug (relative to console behavior) is a
> nuisance.
I'll try to find time, but no
On Wed, 29 Mar 2017 at 13:13 Julien Palard wrote:
> 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.
>
> Wha
On Wed, Mar 29, 2017 at 8:22 AM, Paul Moore wrote:
> On 28 March 2017 at 17:31, Nathaniel Smith wrote:
>> IMO this is a bug, and depending on how many packages are affected it might
>> even call for an emergency 3.6.2. The worst case is that we start getting
>> large numbers of packages uploaded
On 3/29/2017 4:13 PM, Julien Palard via Python-Dev wrote:
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.
https://www.python.org/about/legal/
"If you have any questions, please send them to the legal mailing list
at: le...@pyt
On 29 March 2017 at 02:18, Paul Moore wrote:
> On 28 March 2017 at 12:24, Miro Hrončok wrote:
>> I'd like some clarification on what ABI compatibility we can expect.
>> * Should the ABI be stable across patch releases (so calling
>> PySlice_AdjustIndices from an existing macro would be a bug)?
>
On 30 March 2017 at 15:31, Nick Coghlan wrote:
> On 29 March 2017 at 02:18, Paul Moore wrote:
>> On 28 March 2017 at 12:24, Miro Hrončok wrote:
>>> I'd like some clarification on what ABI compatibility we can expect.
>>> * Should the ABI be stable across patch releases (so calling
>>> PySlice_A
13 matches
Mail list logo
