[GH-ISSUE #393] Dependencies/requirements builder #316

New issue

Closed

opened 2026-02-26 12:21:12 +03:00 by kerem · 4 comments

kerem commented

2026-02-26 12:21:12 +03:00

Owner

Originally created by @SantaLaMuerte on GitHub (May 2, 2023).
Original GitHub issue: https://github.com/brentvollebregt/auto-py-to-exe/issues/393

Is it possible to parse libs from original file and made a requirements txt file with em , when exe file is building. Thnx for project

Originally created by @SantaLaMuerte on GitHub (May 2, 2023). Original GitHub issue: https://github.com/brentvollebregt/auto-py-to-exe/issues/393 Is it possible to parse libs from original file and made a requirements txt file with em , when exe file is building. Thnx for project

kerem closed this issue

2026-02-26 12:21:12 +03:00

kerem commented

2026-02-26 12:21:12 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (May 2, 2023):

👋 Hi, just a reminder that if you haven't read the help post yet, give it a read to see if your issue is covered in it and make sure to follow the debugging section.

Also please note, as stated in the README, if your issue is only associated with your application and not auto-py-to-exe itself, please do not create an issue in this repository - instead, comment on the help post, video or create a new discussion.

@github-actions[bot] commented on GitHub (May 2, 2023): 👋 Hi, just a reminder that if you haven't read [the help post](https://nitratine.net/blog/post/issues-when-using-auto-py-to-exe/) yet, give it a read to see if your issue is covered in it and make sure to follow [the debugging section](https://nitratine.net/blog/post/issues-when-using-auto-py-to-exe/#debugging). Also please note, as stated in the README, if your issue is only associated with your application and not auto-py-to-exe itself, please do not create an issue in this repository - instead, comment on the help [post](https://nitratine.net/blog/post/issues-when-using-auto-py-to-exe/), [video](https://youtu.be/OZSZHmWSOeM) or create a [new discussion](https://github.com/brentvollebregt/auto-py-to-exe/discussions).

kerem commented

2026-02-26 12:21:12 +03:00

Author

Owner

@brentvollebregt commented on GitHub (May 3, 2023):

Not really - an import in a script doesn't tell you which library it comes from. The import could hint where it comes from, but a package's name on PyPI does not have to match how it is imported in a script.

Also you may have written your own script that has the same name as a package in PyPI - which could then add the incorrect package.

@brentvollebregt commented on GitHub (May 3, 2023): Not really - an import in a script doesn't tell you which library it comes from. The import could hint where it comes from, but a package's name on PyPI does not have to match how it is imported in a script. Also you may have written your own script that has the same name as a package in PyPI - which could then add the incorrect package.

kerem commented

2026-02-26 12:21:12 +03:00

Author

Owner

@SantaLaMuerte commented on GitHub (May 3, 2023):

Not really - an import in a script doesn't tell you which library it comes from. The import could hint where it comes from, but a package's name on PyPI does not have to match how it is imported in a script.

Also you may have written your own script that has the same name as a package in PyPI - which could then add the incorrect package.

Found that one , maybe can be implemented
https://github.com/bndr/pipreqs

@SantaLaMuerte commented on GitHub (May 3, 2023): > Not really - an import in a script doesn't tell you which library it comes from. The import could hint where it comes from, but a package's name on PyPI does not have to match how it is imported in a script. > > Also you may have written your own script that has the same name as a package in PyPI - which could then add the incorrect package. Found that one , maybe can be implemented https://github.com/bndr/pipreqs

kerem commented

2026-02-26 12:21:12 +03:00

Author

Owner

@brentvollebregt commented on GitHub (May 3, 2023):

Sorry, I'm not sure why something like this is needed in auto-py-to-exe?

Also looking at the source of that library - it appears that it will set the version of a library to the latest in PyPI. No discredit to the authors, but this could cause an incorrect version of a library to be used. This incorrect versioning would not work with this tool as if the script doesn't run before packaging, it certainly won't run as an exe.

Also the mapping file shows what I was talking about when saying import names can be different to PyPI package names.

@brentvollebregt commented on GitHub (May 3, 2023): Sorry, I'm not sure why something like this is needed in auto-py-to-exe? Also looking at the source of that library - it appears that it will set the version of a library to the latest in PyPI. No discredit to the authors, but this could cause an incorrect version of a library to be used. This incorrect versioning would not work with this tool as if the script doesn't run before packaging, it certainly won't run as an exe. > Also [the mapping file](https://github.com/bndr/pipreqs/blob/master/pipreqs/mapping) shows what I was talking about when saying import names can be different to PyPI package names.