extend chipsec_main search to both py and pyc

[tallu]

No description provided.

[BrentHoltsclaw]

Can the logic be modified to explicitly match only py and pyc files.

[tallu]

Of course. I'll do that. I'm far from being Python expert, but should it be extended to both py, pyc and pyo? On Monday, October 25, 2021, 07:51:51 PM GMT+3, BrentHoltsclaw ***@***.***> wrote: Can the logic be modified to explicitly match only py and pyc files. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android.

[tallu]

Hi I haven't got any reply to my question.Should it be extended to both py, pyc and pyo? Thanks,Tal On Monday, October 25, 2021, 07:51:51 PM GMT+3, BrentHoltsclaw ***@***.***> wrote: Can the logic be modified to explicitly match only py and pyc files. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android.

[npmitche]

Our normal execution of chipsec does not produce .pyo files, so I don't think it's necessary to include them.

[npmitche]

@tallu if you want to open a new PR around this that fixes the issue mentioned in #1357, please do!

[tallu]

@npmitche How can I regenerate the ERROR described here #1357 On Friday, January 28, 2022, 08:50:40 PM GMT+2, Nathaniel Mitchell ***@***.***> wrote: @tallu if you want to open a new PR around this that fixes the issue mentioned in #1357, please do! — Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android. You are receiving this because you were mentioned.Message ID: ***@***.***>

[npmitche]

Hi @tallu, simply running chipsec_main.py twice, the first time builds the extra .pyc files, then on the subsequent runs it sees them and errors out.
pycprlog.txt

[tallu]

Hi  What does it mean to strip out pyc files?How do you do that? Deleting __pycache__ folders is a workaround for this problem.I've added the following lines at the begining of chipsec_main.py and it does the trick... import pathlibimport shutil[shutil.rmtree(p) for p in pathlib.Path('.').rglob('__pycache__')] Regards,Tal On Tuesday, February 1, 2022, 02:13:24 AM GMT+2, Nathaniel Mitchell ***@***.***> wrote: Hi @tallu, simply running chipsec_main.py twice, the first time builds the extra .pyc files, then on the subsequent runs it sees them and errors out. pycprlog.txt — Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android. You are receiving this because you were mentioned.Message ID: ***@***.***>

[npmitche]

Hi @tallu
Sorry for the lack of response. What is your use case for wanting to include .pyc files? Are you moving .pyc files that were cached on a different system without moving the source (.py)? I'm not sure if that's a viable way to run python code.

If you simply want python to use the cached bytecodes (.pyc) instead of using the source (.py), this is done automatically when .pyc files are present and this patch is not needed.