[issue410164] pydoc can't find module in current dir

Change by admin : -- github: None -> 34203 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue35596] Fatal Python error: initfsencoding: unable to load the file system codec zipimport.ZipImportError: can't find module 'encodings'

Serhiy Storchaka added the comment: > When was the last time we had a 3.x.y.z? I don't recall one. My apologies, it seems my memory has tricked me. I thought there was on in the 3.3 branch, but it was just that the third number was bumped again just a month ago after a bugfix release.

[issue35596] Fatal Python error: initfsencoding: unable to load the file system codec zipimport.ZipImportError: can't find module 'encodings'

Ned Deily added the comment: Thanks, Steve. The download page for 3.7.2 has now been updated with the URLs for the modified embeddable files, the CDN caches updated, and the original embeddable download files and their GPG signature files are no longer accessible so references to the

[issue35596] Fatal Python error: initfsencoding: unable to load the file system codec zipimport.ZipImportError: can't find module 'encodings'

Steve Dower added the comment: I've updated the files and sent Ned the info needed to confirm and update the download page. -- ___ Python tracker ___

[issue35596] Fatal Python error: initfsencoding: unable to load the file system codec zipimport.ZipImportError: can't find module 'encodings'

Steve Dower added the comment: Agreed. My plan is to just replace the precompiled ZIP file of the standard library in the embeddable package with one with PYCs missing the "check source" bit that the old zipimport rejects. It's as simple as a 1 line change in a supporting script in

[issue35596] Fatal Python error: initfsencoding: unable to load the file system codec zipimport.ZipImportError: can't find module 'encodings'

Ned Deily added the comment: > It would be weird if building from sources will not give the same > distribution as downloaded from official site. It would be not fair to > alternate distributors. Yes, I agree with that in general but, as I understand it, the change here affects only how

[issue35596] Fatal Python error: initfsencoding: unable to load the file system codec zipimport.ZipImportError: can't find module 'encodings'

Serhiy Storchaka added the comment: It would be weird if building from sources will not give the same distribution as downloaded from official site. It would be not fair to alternate distributors. I think this is a time to release 3.7.2.1. This would be not the first time of using the

[issue35596] Fatal Python error: initfsencoding: unable to load the file system codec zipimport.ZipImportError: can't find module 'encodings'

Ned Deily added the comment: I think we should change the name (post1 is fine), delete the original file, update the file name link in the release page (https://www.python.org/downloads/release/python-372/) to use the new name, and add a sentence or two to the release page describing the

[issue35596] Fatal Python error: initfsencoding: unable to load the file system codec zipimport.ZipImportError: can't find module 'encodings'

Steve Dower added the comment: I can add ".post1" to the version number in the file name, but I'd still want to take down the broken one. And anyone who's generating the download URL will get a broken link, which IMO is just as bad as a broken download when we could fix it. --

[issue35596] Fatal Python error: initfsencoding: unable to load the file system codec zipimport.ZipImportError: can't find module 'encodings'

Steve Dower added the comment: I can add a .post1 into the version number in the zip file? Still want to take the old one down though, and if anyone is using any sort of script to get this file then it'll be just as annoying for the link to be broken as getting a broken download.

[issue35596] Fatal Python error: initfsencoding: unable to load the file system codec zipimport.ZipImportError: can't find module 'encodings'

Steve Dower added the comment: I know how to purge the CDN cache, so that's not an issue. And there's no good reason to leave the old one up. Perhaps we can just add a note to the download page and I'll post on a couple of lists? This is basically a product recall, and those are usually

[issue35596] Fatal Python error: initfsencoding: unable to load the file system codec zipimport.ZipImportError: can't find module 'encodings'

Ned Deily added the comment: CDN caching on python.org is not a problem; we know how to clear out the cache. But I also strongly dislike silent updates of released files so I agree that names should be changed if we do end up agreeing to replace one or more files. --

[issue35596] Fatal Python error: initfsencoding: unable to load the file system codec zipimport.ZipImportError: can't find module 'encodings'

STINNER Victor added the comment: > This is now resolved, and only through modifying the build scripts. Which > means I can take the existing build and republish a fixed embeddable package > without needing a new release. Since Python itself doesn't make, I'm ok to not change the Python

[issue35596] Fatal Python error: initfsencoding: unable to load the file system codec zipimport.ZipImportError: can't find module 'encodings'

Ned Deily added the comment: It seems like this need not trigger a complete new release and, ATM, I'm not aware of any other showstopper problems that would otherwise trigger an early 3.7.3. One question would be how and where to document this change in the build artificat. Suggestions,

[issue35596] Fatal Python error: initfsencoding: unable to load the file system codec zipimport.ZipImportError: can't find module 'encodings'

Steve Dower added the comment: This is now resolved, and only through modifying the build scripts. Which means I can take the existing build and republish a fixed embeddable package without needing a new release. Unless Ned would prefer a complete release? --

[issue35596] Fatal Python error: initfsencoding: unable to load the file system codec zipimport.ZipImportError: can't find module 'encodings'

miss-islington added the comment: New changeset 69f64b67e43c65c2178c865fd1be80ed07f02d3c by Miss Islington (bot) in branch '3.7': bpo-35596: Use unchecked PYCs for the embeddable distro to avoid zipimport restrictions (GH-11465)

[issue35596] Fatal Python error: initfsencoding: unable to load the file system codec zipimport.ZipImportError: can't find module 'encodings'

Steve Dower added the comment: New changeset 872bd2b57ce8e4ea7a54acb3934222c0e4e7276b by Steve Dower in branch 'master': bpo-35596: Use unchecked PYCs for the embeddable distro to avoid zipimport restrictions (GH-11465)

[issue35596] Fatal Python error: initfsencoding: unable to load the file system codec zipimport.ZipImportError: can't find module 'encodings'

Change by Steve Dower : -- pull_requests: +10953, 10954 stage: test needed -> patch review ___ Python tracker ___ ___

[issue35596] Fatal Python error: initfsencoding: unable to load the file system codec zipimport.ZipImportError: can't find module 'encodings'

Change by Steve Dower : -- pull_requests: +10953 stage: test needed -> patch review ___ Python tracker ___ ___ Python-bugs-list

[issue35596] Fatal Python error: initfsencoding: unable to load the file system codec zipimport.ZipImportError: can't find module 'encodings'

Change by Steve Dower : -- pull_requests: +10953, 10954, 10955 stage: test needed -> patch review ___ Python tracker ___ ___

[issue35596] Fatal Python error: initfsencoding: unable to load the file system codec zipimport.ZipImportError: can't find module 'encodings'

Steve Dower added the comment: And I assume now that the reason it broke in 3.7.2 is because the pyc mode for the embeddable distro changed. Which means the right place for tests is in a separate build that uses properly laid out Python rather than testing in the source tree (like what I

[issue35596] Fatal Python error: initfsencoding: unable to load the file system codec zipimport.ZipImportError: can't find module 'encodings'

Steve Dower added the comment: Looks like zipimport in 3.7 always rejected CHECKED_HASH pycs, while in 3.8 it always accepts them (or runs it through a validation process that passes them when the source file doesn't exist - I only confirmed by testing a build, not by walking through the

[issue35596] Fatal Python error: initfsencoding: unable to load the file system codec zipimport.ZipImportError: can't find module 'encodings'

Change by Marc Schlaich : -- nosy: +schlamar ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue35596] Fatal Python error: initfsencoding: unable to load the file system codec zipimport.ZipImportError: can't find module 'encodings'

Steve Dower added the comment: Yes, we've established that zipimport is rejecting .pyc files now, but we need to dig through it to figure out why. I haven't had time yet, but if someone else can then don't wait for me. -- ___ Python tracker

[issue35596] Fatal Python error: initfsencoding: unable to load the file system codec zipimport.ZipImportError: can't find module 'encodings'

wwq added the comment: I have tried zipping the stdlib myself form normal version's "Python37\Lib" with all files were end with ".py"(without "site-packages" of course). And then everything work fine. Maybe the loader only reject ".pyc" file from zip load? -- nosy: +wwqgtxx

[issue35596] Fatal Python error: initfsencoding: unable to load the file system codec zipimport.ZipImportError: can't find module 'encodings'

Nick Coghlan added the comment: Ah, you're right - I missed that the ForceASCII stuff was on the non-Windows side of an ifdef so it's literally impossible for that change to affect Windows, not just highly unlikely. It would be interesting to compare the output of `python -vv` between the

[issue35596] Fatal Python error: initfsencoding: unable to load the file system codec zipimport.ZipImportError: can't find module 'encodings'

Steve Dower added the comment: I took a closer look at the diff since 3.7.1, and I'm not seeing anything either. I suspect we need to step through zipimport/importlib and figure out exactly where it rejects the .pyc files in the zip. -- ___

[issue35596] Fatal Python error: initfsencoding: unable to load the file system codec zipimport.ZipImportError: can't find module 'encodings'

Steve Dower added the comment: None of the code you linked is defined on Windows at all, so it can't be that. Are any stat checks done when there's only a .pyc to import? Could it be deciding that the .pyc is out of date and then failing to find source? --

[issue35596] Fatal Python error: initfsencoding: unable to load the file system codec zipimport.ZipImportError: can't find module 'encodings'

Nick Coghlan added the comment: Reviewing the diff at https://github.com/python/cpython/compare/v3.7.1...v3.7.2 the only item I've spotted that seems like it could even plausibly be related is the tweak at

[issue35596] Fatal Python error: initfsencoding: unable to load the file system codec zipimport.ZipImportError: can't find module 'encodings'

miss-islington added the comment: New changeset bbf695441af9def8a121ff3e245415d9fc0bab9a by Miss Islington (bot) in branch '3.7': bpo-35596: Fix vcruntime140.dll being added to embeddable distro multiple times. (GH-11329)

[issue35596] Fatal Python error: initfsencoding: unable to load the file system codec zipimport.ZipImportError: can't find module 'encodings'

Serhiy Storchaka added the comment: There were no changes in zipimport between 3.7.1 and 3.7.2, and there were just few looking unrelated changes in the import machinery. Maybe this is caused by some changes in the interpreter initialization code? -- nosy: +brett.cannon, eric.snow,

[issue35596] Fatal Python error: initfsencoding: unable to load the file system codec zipimport.ZipImportError: can't find module 'encodings'

miss-islington added the comment: New changeset bbf695441af9def8a121ff3e245415d9fc0bab9a by Miss Islington (bot) in branch '3.7': bpo-35596: Fix vcruntime140.dll being added to embeddable distro multiple times. (GH-11329)

[issue35596] Fatal Python error: initfsencoding: unable to load the file system codec zipimport.ZipImportError: can't find module 'encodings'

Change by Eryk Sun : -- nosy: +serhiy.storchaka stage: patch review -> test needed type: -> crash ___ Python tracker ___ ___

[issue35596] Fatal Python error: initfsencoding: unable to load the file system codec zipimport.ZipImportError: can't find module 'encodings'

Change by miss-islington : -- keywords: +patch, patch, patch pull_requests: +10600, 10601, 10602 ___ Python tracker ___ ___

[issue35596] Fatal Python error: initfsencoding: unable to load the file system codec zipimport.ZipImportError: can't find module 'encodings'

Change by miss-islington : -- keywords: +patch, patch pull_requests: +10600, 10601 ___ Python tracker ___ ___ Python-bugs-list

[issue35596] Fatal Python error: initfsencoding: unable to load the file system codec zipimport.ZipImportError: can't find module 'encodings'

Change by miss-islington : -- keywords: +patch pull_requests: +10600 ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue35596] Fatal Python error: initfsencoding: unable to load the file system codec zipimport.ZipImportError: can't find module 'encodings'

miss-islington added the comment: New changeset 59c2aa25ffc864bf11bf3b3973828f00e268a992 by Miss Islington (bot) (Steve Dower) in branch 'master': bpo-35596: Fix vcruntime140.dll being added to embeddable distro multiple times. (GH-11329)

[issue35596] Fatal Python error: initfsencoding: unable to load the file system codec zipimport.ZipImportError: can't find module 'encodings'

Steve Dower added the comment: Thanks for the extra info, and for confirming that 3.6.8 isn't affected (I hadn't tried that you, so you saved me some work :) ) This is definitely a new zipimport regression in 3.7.2. Thanks for the report. -- keywords: +3.7regression -patch, patch

[issue35596] Fatal Python error: initfsencoding: unable to load the file system codec zipimport.ZipImportError: can't find module 'encodings'

C v.1916 64 bit (AMD64)] on win32 >>> import sys; sys.exit() C:\>\tmp\py372\python Fatal Python error: initfsencoding: unable to load the file system codec zipimport.ZipImportError: can't find module 'encodings' Current thread 0x2614 (most recent call first): C:\>copy \tmp\py36

[issue35596] Fatal Python error: initfsencoding: unable to load the file system codec zipimport.ZipImportError: can't find module 'encodings'

Change by Steve Dower : -- keywords: +patch, patch, patch pull_requests: +10594, 10595, 10596 stage: test needed -> patch review ___ Python tracker ___

[issue35596] Fatal Python error: initfsencoding: unable to load the file system codec zipimport.ZipImportError: can't find module 'encodings'

Change by Steve Dower : -- keywords: +patch, patch pull_requests: +10594, 10595 stage: test needed -> patch review ___ Python tracker ___

[issue35596] Fatal Python error: initfsencoding: unable to load the file system codec zipimport.ZipImportError: can't find module 'encodings'

Change by Steve Dower : -- keywords: +patch pull_requests: +10594 stage: test needed -> patch review ___ Python tracker ___ ___

[issue35596] Fatal Python error: initfsencoding: unable to load the file system codec zipimport.ZipImportError: can't find module 'encodings'

Steve Dower added the comment: Okay, this looks like a zipimport issue. When I extract the "python37.zip" file containing the stdlib and reference the directory it works fine. But no matter what I do to the ZIP I can't get it to run. It seems that zipimport either can't import .pyc files

[issue35596] Fatal Python error: initfsencoding: unable to load the file system codec zipimport.ZipImportError: can't find module 'encodings'

Steve Dower added the comment: Have you tried a proper install as well? Could you do that to rule out any problem on your machine? Are you repackaging anything as part of your app, or are you just testing the package first and getting this error? It looks like you're running from the

[issue35596] Fatal Python error: initfsencoding: unable to load the file system codec zipimport.ZipImportError: can't find module 'encodings'

Change by Ned Deily : -- components: +Windows nosy: +paul.moore, steve.dower, tim.golden, zach.ware ___ Python tracker ___ ___

[issue35596] Fatal Python error: initfsencoding: unable to load the file system codec zipimport.ZipImportError: can't find module 'encodings'

New submission from hyu : >python Fatal Python error: initfsencoding: unable to load the file system codec zipimport.ZipImportError: can't find module 'encodings' There are two vcruntime140.dll with no binary diff. Date Time Attr Size Compressed N

[issue32738] CDLL : Can't find module

Christian Heimes added the comment: Your library is probably missing dependencies. Please use the Python mailing list or IRC to get assistance. bugs.python.org is a bug tracker, not a supported forum. You can find more information about community support forums on

[issue32738] CDLL : Can't find module

Change by twinkim2 <twink...@hanmail.net>: -- title: CDLL : Can't fine module -> CDLL : Can't find module ___ Python tracker <rep...@bugs.python.org> <https://bugs.pyt

Re: ZipImportError: can't find module

In <1e511b73-e984-459c-9311-77bcd...@googlegroups.com> loial <jldunn2...@gmail.com> writes: > What has been working for years suddenly has an error : > zipimport.ZipImportError: can't find module 'mymodule' How is the shell script executed? Is it run interactively,

ZipImportError: can't find module

I am suddenly having a problem with importing a module from a zip file in Python 2.4.1 What has been working for years suddenly has an error : zipimport.ZipImportError: can't find module 'mymodule' PYTHONPATH is correct, it points to the zip file containing mymodule N.B. the python script

Re: Can't Find Module

On Sat, 07 Nov 2009 16:59:29 -, Victor Subervi victorsube...@gmail.com wrote: ImportError: No module named template [snip] I can import this just fine from the python command prompt. So, what gives? Is template.py in your current directory when you run the script from the command

Can't Find Module

Hi; I'm getting this error: Mod_python error: PythonHandler mod_python.publisher Traceback (most recent call last): File /usr/lib64/python2.4/site-packages/mod_python/apache.py, line 299, in HandlerDispatch result = object(req) File

Can't find module named 'svn' in python

Hi, i have a simple test which tries to load 'svn' moddule. # python -c from svn import client Traceback (most recent call last): File string, line 1, in ? ImportError: No module named svn I have checked I have sub-directories 'libsvn', 'svn' under /usr/local/lib/svn-python/ cd

Re: Can't find module named 'svn' in python

My first thought: Check if you have /usr/local/lib/svn-python/ in your PYTHONPATH environment variable (echo $PYTHONPATH). If its missing, set it in the environment. export PYTHONPATH=$PYTHONPATH:/usr/local/lib/svn-python -N [EMAIL PROTECTED] wrote: Hi, i have a simple test which tries to