On Mon, 6 Apr 2020 08:32:34 +1000
Nick Coghlan wrote:
> Hi Musbur,
>
> While python-dev is specifically for core development, the "specific
> interest group" mailing lists are for both change proposals and
> existing usage questions.
>
> I've cc'ed cap
Hello,
(I've asked this question before on python-list but only got scarce
and ultimately unhelpful answers. Although this isn't about Python
development itself, I'm assuming that there is more CPython
knowledge on this list than on the other, so please bear with me.)
I've written a C extension m
On Fri, 20 Mar 2020 20:49:12 -
"Dennis Sweeney" wrote:
> exactly same way (as a character set) in each case. Looking at how
> the argument is used, I'd argue that ``lstrip``/``rstrip``/``strip``
> are much more similar to each other than they are to the proposed
> methods
Correct, but I don'
Depends on what d is.
type({})
So the result is {(1, 2): None}, but the ambiguity comes from the
definition of {}, not from my proposal.
Am 05.02.2020 18:19 schrieb Serhiy Storchaka:
05.02.20 14:27, Musbur пише:
I have one suggestion: Wouldn't it be useful for these operators to
This is a great PEP. Just recently I needed this and was surprised that
nothing of the sort had been implemented yet (I looked for quite some
time).
I have one suggestion: Wouldn't it be useful for these operators to also
accept sets (functionally acting like a dict with None for all values)?
Hi guys,
after I got the whole list into a lather about the merits of
the python-config program, let me rephrase the question:
Is there a "canonical" way of automatically finding the correct
include files and Python runtime library when embedding the Python
interpreter, based on the current virtu
On Thu, 9 Jan 2020 15:18:55 +0100
Victor Stinner wrote:
> Which build command rely on python-config? Is it to cross-compile 3rd
> party C extensions on the host?
Hello, OP speaking here. In two cases I came across this issue. No
cross-compiling involved.
1) To debug a Python C extension I wrote
Hello,
I'm experimenting with package development on different versions of
Python in different virtualenvs. After running "make" I don't do "make
install", but rather I set up virtualenvs by running
/path/to/source/python -m venv env_dir. This works for as long as I
don't need to compile exte
