On Jul 31, 2018, at 15:14, Victor Stinner wrote:
>
> I finished my work on the _PyCoreConfig structure: it's a C structure
> in Include/pystate.h which has many fields used to configure Python
> initialization. In Python 3.6 and older, these parameters were scatted
> around the code, and it was
On Tue, Jul 31, 2018 at 4:15 PM Victor Stinner wrote:
> I finished my work on the _PyCoreConfig structure:
\o/
Thanks for all the good work!
> Right now, the new API is still private. Nick Coghlan splitted the
> initialization in two parts: "core" and "main". I'm not sure that this
> split is
Sounds like i can skip this then. Thx.
Sent from my iPhone
> On 1 Aug 2018, at 17:52, Christian Heimes wrote:
>
>> On 2018-08-01 13:58, Michael wrote:
>> a) I am looking at getting spwd integrated from AIX
>>
>> b) only the parameter sp_pwdp is my concern - as AIX really does not
>> want to
Hi,
On 30 July 2018 at 22:19, Chris Barker via Python-Dev
wrote:
> Oh well. This is a serious usability issue -- but what can you do?
I think that argument clinic knows if the built-in function is
supposed to be a method or a function. It doesn't look too hard to
add a new flag METH_IS_METHOD
Brett Cannon schrieb am 01.08.2018 um 18:17:
> On Tue, 31 Jul 2018 at 13:42 Stefan Behnel wrote:
>> Antoine Pitrou schrieb am 31.07.2018 um 09:45:
>>> Also, a C extension can be built-in (linked statically into the
>>> interpreter), which I think would be hard to do with Cython.
>>
>> Someone
I don’t think there would be any trouble linking in the generated C files. The
built in modules like this just have their *_init() functions called at
startup, so possibly nothing would even change.
Top-posted from my Windows 10 phone
From: Brett Cannon
Sent: Wednesday, 1 August 2018 17:20
To:
On Wed, 1 Aug 2018 09:05:52 -0700
Brett Cannon wrote:
> On Wed, 1 Aug 2018 at 07:47 Terry Reedy wrote:
>
> > On 8/1/2018 6:17 AM, Jeroen Demeyer wrote:
> > > On 2018-07-31 11:12, INADA Naoki wrote:
> > >> Any PEP won't be accepted in few month, because we don't have flow to
> > >> accept
[new thread as this no longer has anything to do with Victor's proposal]
On Tue, 31 Jul 2018 at 13:42 Stefan Behnel wrote:
> Antoine Pitrou schrieb am 31.07.2018 um 09:45:
> > On Tue, 31 Jul 2018 09:27:03 +0200
> > Jeroen Demeyer wrote:
> >> On 2018-07-31 08:58, Antoine Pitrou wrote:
> >>> I
On Tue, 31 Jul 2018 at 15:16 Victor Stinner wrote:
> Hi,
>
> I finished my work on the _PyCoreConfig structure: it's a C structure
> in Include/pystate.h which has many fields used to configure Python
> initialization. In Python 3.6 and older, these parameters were scatted
> around the code, and
On Wed, 1 Aug 2018 at 07:47 Terry Reedy wrote:
> On 8/1/2018 6:17 AM, Jeroen Demeyer wrote:
> > On 2018-07-31 11:12, INADA Naoki wrote:
> >> Any PEP won't be accepted in few month, because we don't have flow to
> >> accept PEPs for now.
> >
> > Is that certain? I haven't been following the
Open an issue as this will surely get forgotten otherwise, then people can
discuss on the issue how to handle this.
On Wed, 1 Aug 2018 at 08:40 Michael wrote:
> I have a build_bot running (yeah me!), and was surprised to see
> test_zlib fail on AIX.
>
> There is not an issue with test_zlib, but
On 2018-08-01 13:58, Michael wrote:
> a) I am looking at getting spwd integrated from AIX
>
> b) only the parameter sp_pwdp is my concern - as AIX really does not
> want to reveal the encrypted password. Rather, AIX will say '!' (meaning
> there is, or should be a shadow password, or '*' - no
a) I am looking at getting spwd integrated from AIX
b) only the parameter sp_pwdp is my concern - as AIX really does not
want to reveal the encrypted password. Rather, AIX will say '!' (meaning
there is, or should be a shadow password, or '*' - no user password).
Would this horribly break
I have a build_bot running (yeah me!), and was surprised to see
test_zlib fail on AIX.
There is not an issue with test_zlib, but I do have a suggestion.
I was getting an error with test_flushes(). On python2-2.7.15 the test
passes and in python3-3.8 (and earlier I expect) the test fails. The
On 8/1/2018 6:17 AM, Jeroen Demeyer wrote:
On 2018-07-31 11:12, INADA Naoki wrote:
Any PEP won't be accepted in few month, because we don't have flow to
accept PEPs for now.
Is that certain? I haven't been following the process discussions, so
I'm just asking the question. For example, given
On 2018-07-31 11:12, INADA Naoki wrote:
Any PEP won't be accepted in few month, because we don't have flow to
accept PEPs for now.
Is that certain? I haven't been following the process discussions, so
I'm just asking the question. For example, given that you are already
looking at PEP 580,
FWIW, it looks like this is the first (earliest) merge commit that
caused the v2.7.4 line to contain
cf86e368ebd17e10f68306ebad314eea31daaa1e:
$ git show -q d26b658f1433a28b611906c078f47bc804a63dd1
commit d26b658f1433a28b611906c078f47bc804a63dd1
Merge: 2d639d5665 f8b9dfd9a1
On Wed, Aug 1, 2018 at 1:16 PM, Jeffrey Zhang wrote:
> I found a interesting issue when checking the Lib/datetime.py implementation
> in python3
>
> This patch is introduced by cf86e368ebd17e10f68306ebad314eea31daaa1e [0].
> But if you
> check the github page[0], or using git tag --contains, you
18 matches
Mail list logo
