Gom Lab Codec Search
Phyllis Sterlin
After going through the python source code I've found that, as the error says, no codec search functions have been registered. Both codec_register and PyCodec_Register are as they should be. It's just that nowhere in the code are any of these functions called.
I don't really know what this means as I still have no idea when and from where these functions should have been called. The code that raises the error is entirely missing from the source of my other python build (3.1.3).
Parts of this have been mentioned before, but in a nutshell this is what worked for my environment where I have multiple Python installs and my global OS environment set-up to point to a different install than the one I attempt to work with when encountering the problem.
Make sure your (local or global) environment is fully set-up to point to the install you aim to work with, e.g. you have two (or more) installs of, let's say a python27 and python33 (sorry these are windows paths but the following should be valid for equivalent UNIX-style paths just as well, please let me know about anything I'm missing here (probably the DLLs path might differ)):
Now, if you intend to work with your python33 install but your global environment is pointing to python27, make sure you update your environment as such (while PATH and PYTHONHOME may be optional (e.g. if you temporarily work in a local shell)):
Note, that you might need/want to append any other library paths to your PYTHONPATH if required by your development environment, but having your DLLs, Lib and site-packages properly set-up is of prime importance.
Ran into the same thing trying to install brew's python3 under Mac OS! The issue here is that in Mac OS, homebrew puts the "real" python a whole layer deeper than you think. You would think from the homebrew output that
would be correct, but invoking $PYTHONPATH/python3 immediately crashes with the abort 6 "can't find encodings." This is because although that $PYTHONHOME looks like a complete installation, having a bin, lib etc, it is NOT the actual Python, which is in a Mac OS "Framework". Do this:
From python3k, the startup need the encodings module, which can be found in PYTHONHOME\Lib directory. In fact, the API Py_Initialize () do the init and import the encodings module.Make sure PYTHONHOME\Lib is in sys.path and check the encodings module is there.
before initialize so that it could find the headers that it needed, where my path was to "...\Anaconda3\". The extra step of calling Py_SetPythonHome was required for me or else I'd end up getting other strange errors where python import files.
There appears to be something going wrong with the release build either failing to include the appropriate codecs or else misidentifying the codec to use for system APIs. Since the python_d executable is working, what does that return for os.getfsencoding()? (Use the C API to call that between your Initialize/Finalize calls)
I had the same issue and found this question. However from the answers here I was not able to solve my problem. I started debugging the cpython code and thought that I might be discovered a bug. Therefore I opened a issue on the python issue tracker.
I compiled the source of CPython 3.7.3 myself on Windows with Visual Studio 2017 together with some packages like e.g numpy. When I start the Python Interpreter I am able to import and use numpy. However when I am running the same script via the C-API I get an ModuleNotFoundError.
So the first thing I did, was to check if numpy is in my site-packages directory and indeed there is a folder named numpy-1.16.2-py3.7-win-amd64.egg. (Makes sense because the python interpreter can find numpy)
C:\Work\build\product\python37.zip has the correct path 'C:\Work\build\product\'. There was just no zip file. All my files and directory were unpacked. So I zipped the files to an archive named python37.zip and this resolved the import error.
Create a new zipimporter instance. 'archivepath' must be a path-like object to a zipfile, or to a specific path inside a zipfile. For example, it can be '/tmp/myimport.zip', or '/tmp/myimport.zip/mydirectory', if mydirectory is a valid directory inside the archive. 'ZipImportError' is raised if 'archivepath' doesn't point to a valid Zip archive. The 'archive' attribute of the zipimporter object contains the name of the zipfile targeted.
So for me it seems that the C-API expects the path set with Py_SetPath to be a path to a zipfile. Is this expected behaviour or is it a bug? If it is not a bug is there a way to changes this so that it can also detect directories?
PS: The ModuleNotFoundError did not occur for me when using Python 3.5.2+, which was the version I used in my project before. I also checked if I had set any PYTHONHOME or PYTHONPATH environment variables but I did not see one of them on my system.
The short answer is that you need to make sure Python can find the Lib/encodings directory, typically by putting the standard library in sys.path. Py_SetPath clears all inferred paths, so you need to specify all the places Python should look. (The rules for where Python looks automatically are complicated and vary by platform, which is something I'm keen to fix.)
Paths that don't exist are okay, and that's the zip file. You can choose to put the stdlib into a zip, and it will be found automatically if you name it the default path, but you can also leave it unzipped and reference the directory.
I had the problem and was tinkering with different solutions mentioned here. Since I was running my project from Visual Studio, apparently, I needed to set the environment path inside Visual Studio and not the system path.
In my cases, for windows, if you have multiple python versions installed, if PYTHONPATH is pointing to one version the other ones didn't work. I found that if you just remove PYTHONPATH, they all work fine
For those working in Visual Studio simply add the include, Lib and libs directories to the Include Directories and Library Directories under Projects Properties -> Configuration Properties > VC++ Directories :
Make sure the PYTHONHOME environment variable is set to the Python interpreter you want to use. The C++ projects in Visual Studio rely on this variable to locate files such as python.h, which are used when creating a Python extension.
At the moment search will return a distinct list of songs for the album foo, but they explode into dupes when dragged to a playlist. I then have to weed out the unwanted dupes with control-clicking after determining which coded is which.
A codec can consist of two parts: an encoder that compresses the media file (encoding) and a decoder that decompresses the file (decoding). Some codecs include both parts, and other codecs only include one of them.
In the About Windows Media Player dialog box, select Technical Support Information. Your web browser will open a page that includes a lot of detailed info about the related binary files, codecs, filters, plug-ins, and services installed on your PC. This info should help you troubleshoot problems.
There are hundreds of audio and video codecs in use today. Some have been created by Microsoft, but the vast majority of codecs were created by other companies, organizations, and individuals. By default, the Windows operating system and the Player include a number of the most popular codecs, such as Windows Media Audio, Windows Media Video, and MP3.
However, there might be times when you want to play content that was compressed by using a codec that Windows or the Player doesn't include by default. In many cases, you can download the necessary codec from the web for free or for a fee. And, in some cases, the Player can automatically use the codecs installed by other digital media playback and creation programs on your computer.
If you know the name of the codec or its ID (known as a FourCC identifierfor video codecs or a WaveFormat identifierfor audio codecs), try searching the internet for it. You can often go to a codec manufacturer's website to download the most recent version of a codec. If you don't know the missing codec's name or ID, see How do I tell which codec was used to compress a file and what format a file is in?
Use caution when installing codecs that you find on the internet, particularly some of the free codec packs that claim to include codecs from a wide variety of companies or organizations. There are known compatibility issues with some of the components in these codec packs, and these can trigger serious playback problems in Windows Media Player and other players, cause system corruption, and make it difficult for Microsoft Support to diagnose and troubleshoot playback issues.
Therefore, we strongly discourage you from installing these codec packs and recommend that you remove them if you have installed them and are having problems with the Player. Install codecs, filters, and plug-ins only from trusted sources, such as the provider's official website. Even then, use caution: some codec providers offer minimal customer support. Before installing any digital media components, set up a system restore point. This lets you return to your original system configuration, if necessary.
To determine what codec was used with a specific file, play the file in the Player, if possible. While the file is playing, right-click the file in the library, and then select Properties. On the File tab, look at the Audio codec and Video codec sections.
You might be able to tell the format of a file by looking at the file name extension (such as .wma, .wmv, .mp3, or .avi). However, there are limits to this approach. Many programs create files with custom file extensions. And it's possible for anyone to rename a file without changing the file's format. A file with an .mpg or .dvr-ms extension, for example, is usually just an AVI file that's been compressed by using some version of an MPEG video codec.
A DVD decoder is another name for an MPEG-2 decoder. The content on DVD-Video discs is encoded in the MPEG-2 format, as is the content in DVR-MS files (Microsoft Recorded TV Shows) and some AVI files. To play these items in the Player, you need to have a compatible DVD decoder installed on your computer.
7fc3f7cf58