> The Python Foundation needs to adopt or create standard and supported ways of doing things
The Python community has adopted or created a standard way of doing things for the (checks calendar) fourth or fifth time now.
The Python community has adopted or created a standard way of doing things for the (checks calendar) fourth or fifth time now.
It seems crazy to me that we don't have this yet.
python setup.py build_ext --inplace
When I include the library from a project that uses it, the same `pip install' command that brings the library in also performs all the compilation described by my setup.py.
All I'd need to move away from deprecated syntax entirely is a way to build the module when I'm testing it within it's own source directory. Until then I won't be changing anything.
[0]: There should be one-- and preferably only one --obvious way to do it. (from the zen of python)
Unfortunately, each response had a different recommendation. I wish I could find that thread again.
We have been talking about how to support customers who want to use python. At least for me it isn't very appealing, seems like it could take a lot of attention to keep up with what's expected.