importlib.metadata.PackageNotFoundError Nuitka

[abdullah-albanna]

Bug report

Your issue may already be reported!
Please check out our active issues before creating one.

Expected Behavior

It should work with Nuitka just fine

Current Behavior

I get importlib.metadata.PackageNotFoundError: No package metadata was found for thread

Is this a regression?

Possible Solution

They say it might be the metadata thing

Steps to Reproduce (for bugs)

1. Nuitka issues 1793

Context

I'm trying to include thread in my nuitka build because it has things I want, but cannot because of this

Your Environment

• Version used: 2.0.4
• Python version:3.11
• Link to your project: still working on it
• Operating System and version (desktop or mobile):Windows 10

[caffeine-addictt]

@abdullah-albanna
Hey, thanks for raising this. I'll have a look into it.

If you could provide a step by step to reproduce this, it would also help :>

[abdullah-albanna]

@caffeine-addictt
If you just use the thread module normally

and compile it with nuitka (any version would trigger this), you would get this error once upon opening the newly compiled binary.

now I do know that it is fixable to just use an older version of python (3.6 and below), I haven't tested it yet though.

Pretty sure is because of metadata.distribution and metadata_distribution!.

I'd love this getting fixed, I think thread is awesome

[caffeine-addictt]

@abdullah-albanna
Thanks.

Perhaps it's a windows thing?
I tested compiling and running on archlinux on python3.11 and python3.13. No issues.

[abdullah-albanna]

@caffeine-addictt
might, I'll try on arch and mac right now

[caffeine-addictt]

@abdullah-albanna

If its still non-reproducible, I'm willing to revert back to manually incrementing the version numbers.

(I seriously need to create an auto increment script 🤣)

[caffeine-addictt]

@abdullah-albanna

It's also compiling and running perfectly fine on python3.11 on my windows machine.

Are you using nuitka latest version?

[abdullah-albanna]

@caffeine-addictt

Okay, my other machines are acting weird, couldn't compile on it :(

anyway, I found out that it works if compiled without the --standalone

compile yours like so, nuitka --standalone py_file.py

you'd see that error

[caffeine-addictt]

@abdullah-albanna

Ah, I see. I can reproduce it now.

[abdullah-albanna]

@caffeine-addictt

Yeah, you should try with an older version of python and work you way from there to see what's wrong with it

[caffeine-addictt]

@abdullah-albanna

If its still non-reproducible, I'm willing to revert back to manually incrementing the version numbers.

(I seriously need to create an auto increment script 🤣)

Think I'll go with this. Tested it out with v2.0.1, the last version before I had importlib resolve the version number, and it compiles with the standalone flag

[abdullah-albanna]

@caffeine-addictt

Great, that works.