On 27 July 2018 at 20:23, Rob Boehne wrote:
> Why would a VIM build refer to the export file for python?
Because vim includes an optional embedded Python interpreter.
Paul
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman
Why would a VIM build refer to the export file for python?
From: Python-Dev on behalf
of "WILSON, MICHAEL"
Date: Friday, July 27, 2018 at 10:27 AM
To: "python-dev@python.org"
Cc: "WILSON, MICHAEL"
Subject: [DLFILTER] [Python-Dev] Exporting Python functions on AIX
All,
My excuse if this is n
Yes, all symbols starting with _Py are private and must not be used outside
CPython internals.
Victor
Le vendredi 27 juillet 2018, WILSON, MICHAEL a
écrit :
> All,
>
> My excuse if this is not the appropriate list for a question essentially
concerning the AIX port of Python.
>
> The current port
ACTIVITY SUMMARY (2018-07-20 - 2018-07-27)
Python tracker at https://bugs.python.org/
To view or respond to any of the issues listed below, click on the issue.
Do NOT respond to this message.
Issues counts and deltas:
open6740 ( +6)
closed 39260 (+73)
total 46000 (+79)
Open issues w
All,
My excuse if this is not the appropriate list for a question essentially
concerning the AIX port of Python.
The current port of Python for AIX includes composing an export file
(/lib/python2.7/config/python.exp) in which there are a number of functions
starting "Py_" or "_Py_".
The Vim p
On Fri, Jul 27, 2018 at 4:48 PM Chris Jerdonek wrote:
>
> On Fri, Jul 27, 2018 at 6:41 AM, Giampaolo Rodola' wrote:
> >
> > Being TESTFN a global name it appears not suited for parallel testing.
>
> It was designed for parallel testing though:
>
> # Disambiguate TESTFN for parallel testing, while
On Fri, Jul 27, 2018 at 6:41 AM, Giampaolo Rodola' wrote:
>
> Being TESTFN a global name it appears not suited for parallel testing.
It was designed for parallel testing though:
# Disambiguate TESTFN for parallel testing, while letting it remain a valid
# module name.
TESTFN = "{}_{}_tmp".format
On Thu, Jul 26, 2018 at 12:16 AM Tim Golden wrote:
>
> I'm just easing back into core development work by trying to get a
> stable testing environment for Python development on Windows.
>
> One problem is that certain tests use support.TESTFN (a local directory
> constructed from the pid) for outp
Hello all,
since my latest benchmark for PEP 580 [1] involved SageMath, which is
quite a big project, I instead propose a much simpler benchmark
involving mistune.
mistune [2] is a Markdown parser implemented in the Python language. It
optionally allows Cython compilation. It doesn't use any