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
imp.py: load_package() appends to its own loop variable #74830
Comments
On OpenWrt, the Python & Python3 are shipped with bytecodes [also, bytecode compiling is disabled by default]. I got a report of an issue with virtualenv on Python3, that had a weird path: the The fix is here in the patch file: |
Three things. One, the imp module is deprecated, so please don't use it. Two, all undocumented functions in the imp module are considered unsupported, so double-please don't use imp.load_package(). :) Three, we can't look at that patch without the person supplying it signing Python's CLA as we risk running afoul of things legally. |
path = os.path.join(path, '__init__'+extension)
Damn. You guys are more corporate than... <scratching on forehead>... anyway. Please tell me, how to send you my signed CLA. To resolve your first 2 notes: I am not using the imp module, nor the imp.load_package() function. But, virtualenv uses it in it's latest release [15.1.0]. But that's not the actual code that's used. So, maybe we can tell them not to use it, but let's see. While I'm here, maybe I could use this opportunity to start sending a few more patches from the OpenWrt/LEDE package build. |
Alexandru: You'll find the PSF Contributor Agreement at https://www.python.org/psf/contrib/contrib-form/ . |
I already completed those steps. It only mentions "Finally, click the "eSign" button to have the form sent to the PSF Secretary, Ewa Jodlowska." It's unclear from there-on if my patch is acceptable, or whether I can submit it [or anything], wait for a reply ; basically, how to continue once the form is signed. |
Yes, that's all you needed to do. She updated your status in the tracker (you now have the CLA signed '*' next to your name). |
Yes, we're as corporate as an open source project that doesn't have enough funding to be able to defend against a lawsuit but is big enough that simply shutting down would really suck for millions of people. ;) Anyway, your CLA signing came through so now we just need a pull request on GitHub or a patch. As for virtualenv still using a deprecated, hidden API, that's bad on them and should probably be reported to them directly. |
FWIW, I took a look over the virtualenv repo. And a PR to address it Though, it seems like they still want to keep |
Admittedly, that PR refers to |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: