-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PEP 541 Request: pcntl #4929
Comments
Python ask which would make this irrelevant for (future) python version python/cpython#125568 |
As we can see the Python core route is likely to be slow |
Hi @Lewiscowles1986, I need more clarifications because as of right now, your request doesn't seem to really fall under a PEP 541 request. Are you trying to publish a package name but it's already taken? Or are you getting an error that the name is "forbidden" or "prohibited?" Looking into your issue/discussion on python/cpython, however, it sounds like you wish to make some type of improvement in the error message output for fcntl. But, we don't release standard library names for obvious reasons, and feature requests of that nature are not related to PEP 541 requests. |
Hi @Thespi-Brain happy new year. My understanding was that PEP-541 related to the reserved names, and I needed to make a request under PEP-541 if I wanted to publish a shim package to improve user experience. I'm so sorry to have taken your time if this is incorrect. I wanted to fully explore options available. I've not actually made any headway into cpython edits, but the shim package, which just gives windows users a better error. Now I'm not a regular windows user, and just had a wave of energy / anger due to how AWFUL the package mentioned error messages were, particularly for users with less experience. I Found the docs to be borderline beligerant on OS interface differences, which I accept might be too large a can of worms to open here. I Have successfully negotiated edits to the library using pcntl as a transitive dependency via amoffat/sh#740, but solving in each down-stream package seems an inefficient way to solve a central issue. I'm fine if we decide this request is untennable, to close it, as it could focus future energy. Please just close if this isn't a discussion that will help either of us. Thank you for your time. |
Project to be claimed
pcntl
: (standard library)Your PyPI username
LewisCowles1986
: https://pypi.org/user/LewisCowles1986/Reasons for the request
pcntl
throws a module not found error for Windows users (or anyone not on Linux or Mac)Those users think it's pythons fault. (I know it's not)
I've got a pcntl package which on windows gives a more useful error. Eventually I'd like to upstream it, but first I have to publish it. On OSX it doesn't break anything as it uses sys_meta hooks.
Maintenance or replacement?
Maintenance
Source code repositories URLs
https://github.com/Lewiscowles1986/python-fcntl
Contact and additional research
[email protected]
I've looked and found that fcntl is deliberately not part of python for windows. I think this is a mistaken approach, as it makes the error message less clear.
Code of Conduct
The text was updated successfully, but these errors were encountered: