On 5 August 2018 at 00:46, Stefan Behnel wrote:
> Antoine Pitrou schrieb am 04.08.2018 um 15:57:
>> Actually, I think testing the C API is precisely the kind of area where
>> you don't want to involve a third-party, especially not a moving target
>> (Cython is actively maintained and generated
Antoine Pitrou schrieb am 04.08.2018 um 15:57:
> Le 04/08/2018 à 15:13, Nick Coghlan a écrit :
>>
>> It'd be *really* nice to at least be able to write some of the C API
>> tests directly in Cython rather than having to fiddle about with
>> splitting the test between the regrtest parts that
Hi Nick,
Le 04/08/2018 à 15:13, Nick Coghlan a écrit :
>
> It'd be *really* nice to at least be able to write some of the C API
> tests directly in Cython rather than having to fiddle about with
> splitting the test between the regrtest parts that actually define the
> test case and the
On 31 July 2018 at 17:45, Antoine Pitrou wrote:
> On Tue, 31 Jul 2018 09:27:03 +0200
> Jeroen Demeyer wrote:
>> On 2018-07-31 08:58, Antoine Pitrou wrote:
>> > I think Stefan is right that we
>> > should push people towards Cython and alternatives, rather than direct
>> > use of the C API (which
On 4 August 2018 at 05:34, Jeroen Demeyer wrote:
> On 2018-07-30 17:28, Nick Coghlan wrote:
>>
>> I would, and I think it would make sense for the PEP to cite improving
>> consistency (and reducing code duplication?) in that regard as an
>> advantage of the PEP.
>
>
> I'm not sure to which PEP
On 4 August 2018 at 08:37, Victor Stinner wrote:
> It seems like the PEP 432 proposes an API designed from scratch as the
> target API. I started from the 28 years old C code and I tried to
> cleanup the code. Our method is different, so it's not surprising that
> the result is different :-)
No,
On 3 August 2018 at 01:59, Victor Stinner wrote:
> 2018-08-02 1:18 GMT+02:00 Eric Snow :
>> The "core" config is basically the config for the runtime. In fact,
>> PEP 432 renamed "core" to "runtime". Please keep the firm distinction
>> between the runtime and the (main) interpreter.
>
> There
On 2 August 2018 at 19:49, Victor Stinner wrote:
> About that, I'm working on a subproject: abandon Py_xxx global
> configuration variables to replace them with accessing
> interpreter->core_config->xxx. I'm not sure yet if it's a good idea or
> not, but it would allow to have two interpreters to
On 1 August 2018 at 08:14, 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 it
