On 27 February 2017 at 14:03, David Mertz wrote:
> Could we have side-by-side English and whatever translated language? Then
> also use some sort of typographic indicator like color to show when the
> translation is out of date?
>
This kind of interface is what services like Transifex and Zanata
On 27 February 2017 at 06:44, Brett Cannon wrote:
>
>
> On Sun, 26 Feb 2017 at 02:20 Xavier de Gaye wrote:
>
>> In PR 218 [1], INADA Naoki wrote:
>> > I think attributes of Python's code object is implementation detail,
>> even
>> > though PyPy follows.
>> > But it's not big problem until the
Could we have side-by-side English and whatever translated language? Then
also use some sort of typographic indicator like color to show when the
translation is out of date?
On Feb 26, 2017 6:39 PM, "Rob Cliffe" wrote:
>
>
> On 24/02/2017 12:20, Berker Peksağ wrote:
>
>> On Thu, Feb 23, 2017 at
On 24/02/2017 12:20, Berker Peksağ wrote:
On Thu, Feb 23, 2017 at 12:01 AM, Victor Stinner
wrote:
2017-02-22 19:04 GMT+01:00 Serhiy Storchaka :
What percent of lines is changed between bugfix releases? Feature releases?
My largest apprehension is that the documentation can be outdated and
q
I had previously announced tomorrow as the date for the release candidate of
our first 3.6 maintenance release. But, with the switchover to the new
GitHub-based development process, there are a number of changes needed behind
the scenes to our release production process and I think the release
On Sat, 25 Feb 2017 at 11:59 INADA Naoki wrote:
> Yes, right place to discussion is one of important things what I want.
> I haven't know about i18n-sig. Is it better than docs-sig?
>
Probably not (I honestly forgot about docs-sig).
>
>
> Another thing I want is agreement to use project name
On Sun, 26 Feb 2017 at 02:20 Xavier de Gaye wrote:
> In PR 218 [1], INADA Naoki wrote:
> > I think attributes of Python's code object is implementation detail,
> even
> > though PyPy follows.
> > But it's not big problem until there are some Python implementation
> > having different code imp
In PR 218 [1], INADA Naoki wrote:
> I think attributes of Python's code object is implementation detail, even
> though PyPy follows.
> But it's not big problem until there are some Python implementation
> having different code implementation.
Python's code object attributes are described in the D
