[GH-ISSUE #462] data include skips empty folders #366

Closed
opened 2026-02-26 12:21:21 +03:00 by kerem · 6 comments
Owner

Originally created by @wimmatthijs on GitHub (Feb 21, 2024).
Original GitHub issue: https://github.com/brentvollebregt/auto-py-to-exe/issues/462

Quick Checks

  • I have read the help post
  • I have searched other issues, looking for an issue similar to mine
  • I have made sure my application/script runs before trying to package

Describe the bug

the "bug" is pretty simple, if you include a data folder, empty folders are omitted.
my program goes through a premade structure of folders, that can or cannot be empty.
I know it would be best practice to check if folders exist before trying to open any, but on the other hand i would expect data that is added to the project to be added as is, and not omit the empty folders.
For me the folder structure, even empty, is my data.

To Reproduce

open a folder in python script, include that folder empty in your additional files

Expected behavior

include empty folders

Your Environment:

  • Python venv Python=3.12.2 and bottle=0.12.25
  • auto-py-to-exe version 2.42.0
  • PyInstaller version 6.4.0
  • Eel version 0.16.0
Originally created by @wimmatthijs on GitHub (Feb 21, 2024). Original GitHub issue: https://github.com/brentvollebregt/auto-py-to-exe/issues/462 **Quick Checks** - [x] I have read the [help post](https://nitratine.net/blog/post/issues-when-using-auto-py-to-exe) - [x] I have [searched other issues](https://github.com/brentvollebregt/auto-py-to-exe/issues?q=is%3Aissue+), looking for an issue similar to mine - [x] I have made sure my application/script runs before trying to package **Describe the bug** the "bug" is pretty simple, if you include a data folder, empty folders are omitted. my program goes through a premade structure of folders, that can or cannot be empty. I know it would be best practice to check if folders exist before trying to open any, but on the other hand i would expect data that is added to the project to be added as is, and not omit the empty folders. For me the folder structure, even empty, is my data. **To Reproduce** open a folder in python script, include that folder empty in your additional files **Expected behavior** include empty folders **Your Environment:** - Python venv Python=3.12.2 and bottle=0.12.25 - auto-py-to-exe version 2.42.0 - PyInstaller version 6.4.0 - Eel version 0.16.0
kerem 2026-02-26 12:21:21 +03:00
  • closed this issue
  • added the
    Stale
    label
Author
Owner

@github-actions[bot] commented on GitHub (Feb 21, 2024):

👋 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.

<!-- gh-comment-id:1956689273 --> @github-actions[bot] commented on GitHub (Feb 21, 2024): 👋 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).
Author
Owner

@brentvollebregt commented on GitHub (Feb 22, 2024):

I'm not sure myself if PyInstaller supports this - this hints maybe not (but it is quite old)

<!-- gh-comment-id:1959059335 --> @brentvollebregt commented on GitHub (Feb 22, 2024): I'm not sure myself if PyInstaller supports this - [this](https://github.com/pyinstaller/pyinstaller/issues/4708#issuecomment-596155287) hints maybe not (but it is quite old)
Author
Owner

@wimmatthijs commented on GitHub (Feb 22, 2024):

Okay, no problem, would have been nice if a fox was possible to avoid some
curses in the future.

But two pretty straightforward fixes are possible.

  1. Put dummy placeholder files
  2. Selfcheck the folder structure.

I'll do number two in case somebody mingles with it, it will be fixed every
time.

On Thu, Feb 22, 2024, 10:41 AM Brent Vollebregt @.***>
wrote:

I'm not sure myself if PyInstaller supports this - this
https://github.com/pyinstaller/pyinstaller/issues/4708#issuecomment-596155287
hints maybe not (but it is quite old)


Reply to this email directly, view it on GitHub
https://github.com/brentvollebregt/auto-py-to-exe/issues/462#issuecomment-1959059335,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKIAQ4UHM4YHET4JTFRGUT3YU4HELAVCNFSM6AAAAABDTCVXQGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNJZGA2TSMZTGU
.
You are receiving this because you authored the thread.Message ID:
@.***>

<!-- gh-comment-id:1959092004 --> @wimmatthijs commented on GitHub (Feb 22, 2024): Okay, no problem, would have been nice if a fox was possible to avoid some curses in the future. But two pretty straightforward fixes are possible. 1. Put dummy placeholder files 2. Selfcheck the folder structure. I'll do number two in case somebody mingles with it, it will be fixed every time. On Thu, Feb 22, 2024, 10:41 AM Brent Vollebregt ***@***.***> wrote: > I'm not sure myself if PyInstaller supports this - this > <https://github.com/pyinstaller/pyinstaller/issues/4708#issuecomment-596155287> > hints maybe not (but it is quite old) > > — > Reply to this email directly, view it on GitHub > <https://github.com/brentvollebregt/auto-py-to-exe/issues/462#issuecomment-1959059335>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AKIAQ4UHM4YHET4JTFRGUT3YU4HELAVCNFSM6AAAAABDTCVXQGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNJZGA2TSMZTGU> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> >
Author
Owner

@brentvollebregt commented on GitHub (Feb 22, 2024):

Potentially during your build process, you could remove the dummy placeholder files before compressing for distribution

<!-- gh-comment-id:1959133312 --> @brentvollebregt commented on GitHub (Feb 22, 2024): Potentially during your build process, you could remove the dummy placeholder files before compressing for distribution
Author
Owner

@github-actions[bot] commented on GitHub (Mar 25, 2024):

This issue is stale because it has been open for 60 days with no activity. Remove stale label or comment on this issue or it will be closed in 5 days.

<!-- gh-comment-id:2017031019 --> @github-actions[bot] commented on GitHub (Mar 25, 2024): This issue is stale because it has been open for 60 days with no activity. Remove stale label or comment on this issue or it will be closed in 5 days.
Author
Owner

@github-actions[bot] commented on GitHub (Mar 31, 2024):

Closing issue due to no activity in more than 60 days.

<!-- gh-comment-id:2028515980 --> @github-actions[bot] commented on GitHub (Mar 31, 2024): Closing issue due to no activity in more than 60 days.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/auto-py-to-exe#366
No description provided.