On 2018-11-21, 14:54 GMT, Benjamin Peterson wrote:
> In Python 3, there is no underlying FILE* because the io
> module is implemented using fds directly rather than C stdio.
OK, so the proper solution is to kill all functions which expect
FILE, and if you are anal retentive about stability of
Please open a bug report once you have such issue ;-)
Victor
Le mer. 21 nov. 2018 à 15:56, Matěj Cepl a écrit :
>
> On 2018-11-19, 11:59 GMT, Stefan Krah wrote:
> > In practice people desperately *have* to use whatever is
> > there, including functions with underscores that are not even
> >
On Wed, Nov 21, 2018, at 06:53, Matěj Cepl wrote:
> On 2018-11-19, 11:59 GMT, Stefan Krah wrote:
> > In practice people desperately *have* to use whatever is
> > there, including functions with underscores that are not even
> > officially in the C-API.
>
> Yes, there are some functions which
On 2018-11-19, 11:59 GMT, Stefan Krah wrote:
> In practice people desperately *have* to use whatever is
> there, including functions with underscores that are not even
> officially in the C-API.
Yes, there are some functions which evaporated and I have never
heard a reason why and how I am
Le mer. 21 nov. 2018 à 12:11, Antoine Pitrou a écrit :
> You mean the same API can compile to two different things depending on
> a configuration?
Yes, my current plan is to keep #include but have an opt-in
define to switch to the new C API.
> I expect it to be error-prone. For example, let's
On Tue, 20 Nov 2018 23:17:05 +0100
Victor Stinner wrote:
> Le mar. 20 nov. 2018 à 23:08, Stefan Krah a écrit :
> > Intuitively, it should probably not be part of a limited API, but I never
> > quite understood the purpose of this API, because I regularly need any
> > function that I can get my
