'env LANG=C python3.6 setup.py build' fails about platformdirs HOT 5 CLOSED

I should have added that the culprit characters are the "LATIN SMALL LETTER A WITH ACUTE" characters in setup.cfg.

from platformdirs.

Hello.

Running setup.py directly is long discouraged. Does this happen when using python -m build?

from platformdirs.

https://blog.ganssle.io/articles/2021/10/setup-py-deprecated.html

from platformdirs.

Running setup.py directly is long discouraged. Does this happen when using python -m build?

python3.6 -m build (when it eventually completes in a ~250x longer span of time than setup.py build) does not produce the error (whether LANG=C or other). But then spinning in a circle singing Itsy Bitsy Spider over and over doesn't produce an error either. Neither of those things does what 'setup.py build' does (or, if I understand what you are trying to say in this thread and the linked article, "used to do" since it is kinda, sorta vaguely deprecated(ish)).

As far as the speed of this operation, multiply this times 100s of python packages and now we're talking about an operation that used to take minutes will now take hours. It used to be a nice feature of most python packages that they took almost no time to build / install from source. Maybe there's a better way in the new in the new world order, but I don't see it yet.

After reading the linked article, the suggested replacement(s) for 'setup.py install --prefix' (as regular user) is even worse (there isn't one that I can see).

from platformdirs.

To elaborate -- this package supports the currently supported ways to build packages, which is the above, and not running setup.py. If you have concerns with those modern ways, you may certainly want to take those to the respective issue trackers of each replacement, and it may be they have interest in improving performance, usability, or otherwise. Here though, we'll support what's current.

from platformdirs.