Document __spec__.location 'frozen' value#18686
Document __spec__.location 'frozen' value#18686Cheaterman wants to merge 1 commit intopython:masterfrom
Conversation
As noted in https://docs.python.org/3/whatsnew/3.4.html : « If you must know that a module comes from frozen code then you can see if the module’s __spec__.location is set to 'frozen', check if the loader is a subclass of importlib.machinery.FrozenImporter, or if Python 2 compatibility is necessary you can use imp.is_frozen(). »
|
Hello, and thanks for your contribution! I'm a bot set up to make sure that the project can legally accept this contribution by verifying everyone involved has signed the PSF contributor agreement (CLA). Recognized GitHub usernameWe couldn't find a bugs.python.org (b.p.o) account corresponding to the following GitHub usernames: This might be simply due to a missing "GitHub Name" entry in one's b.p.o account settings. This is necessary for legal reasons before we can look at this contribution. Please follow the steps outlined in the CPython devguide to rectify this issue. You can check yourself to see if the CLA has been received. Thanks again for the contribution, we look forward to reviewing it! |
|
CLA signed by the way :-) |
|
Should I maybe create an issue on bugs.python.org ? |
|
@Cheaterman nope, a bug report isn't necessary for a doc fix like this. |
|
@warsaw @ericsnowcurrently @ncoghlan @encukou what do you all think of updating the language reference to say that |
|
Frozen modules are a CPython-specific feature, no? |
|
Based on the fact that frozen modules are specific to CPython and not the language, I'm going to close this. Thanks for the PR regardless, @Cheaterman ! |
|
Likewise, thanks to you for your consideration :-)
Le jeu. 26 mars 2020 à 18:42, Brett Cannon <notifications@github.com> a
écrit :
… Closed #18686 <#18686>.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#18686 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAANLNSQEHHKMXKB2PQ6TXTRJOHZVANCNFSM4K5SY5BA>
.
|
|
Where does this information belong? If the issue is that it is CPython specific then wouldn't that just warrant a disclaimer explaining such? Also, |
|
@altendky the importlib docs is a relevant place for this. |
As noted in https://docs.python.org/3/whatsnew/3.4.html :
« If you must know that a module comes from frozen code
then you can see if the module’s
__spec__.locationisset to 'frozen', check if the loader is a subclass of
importlib.machinery.FrozenImporter, or if Python 2
compatibility is necessary you can use imp.is_frozen(). »