[PyInstaller] KeyError: 'unsupported extension: .hex' about hexrec HOT 7 CLOSED

I can confirm that, there must be a problem with how pyinstaller manages entry points, because it works when launched via Python itself.

The point is hexrec registers file types via the hexrec_types list provided to setuptools.setup(entry_points=...). For some reason, that list is not being read by the hexrec package embedded in the generated executable.

I'm not sure I'm able to fix that, or rather create some workaround.

from hexrec.

Here I found something that seems to work:
pyinstaller/pyinstaller#3050

I will commit changes soon.

from hexrec.

@rajanimindteck: tested locally with the latest commit: 39e1096

Please confirm to close the issue.

from hexrec.

PyInstaller issue is solved with this commit.

from hexrec.

@TexZK: Issue is not fixed for me even when using commit 39e1096.
In contrast to OP I do not try to generate an .exe for hexrec itself, but import hexrec in another module and try to package that as an executable file.

mymodule.py

    import hexrec.records as hr
    ... 

• Create and activate a venv
• Upgrade pip
• Install hexrec (commit 39e1096) and pyinstaller
• pyinstaller -y --name mymodule ./mymodule.py
• Compiled exe throws error:

KeyError: 'unsupported extension: .s19'
[13216] Failed to execute script mymodule

from hexrec.

@kiesner thanks for pointing this out. I actually have the same problem with an utility script I use at work.
In order to let pyinstaller compile the script into an executable file, I added the following stuff at the beginning as a workaround:

import sys
from typing import MutableMapping
from typing import Type
from typing import cast

import hexrec.records as hr


# Fix missing entry_points with pyinstaller
if hasattr(sys, 'frozen') and getattr(sys, 'frozen') and hasattr(sys, '_MEIPASS'):
    import hexrec.formats.intel
    import hexrec.formats.motorola
    _record_types = cast(MutableMapping[str, Type[hr.Record]], hr.RECORD_TYPES)
    _record_types.update({
        'intel':    hexrec.formats.intel.Record,
        'motorola': hexrec.formats.motorola.Record,
    })

I hope to find a consistent way to make entry_points work, otherwise I will switch back to the old solution, where I populated hexrec.records.RECORD_TYPES manually to their defaults, instead of relying on entry_points.

from hexrec.

@kiesner You can try again with the latest commit (57f0e31)

from hexrec.