mirror of
https://github.com/brentvollebregt/auto-py-to-exe.git
synced 2026-04-25 19:55:49 +03:00
[GH-ISSUE #291] avoid writing into fallback folder #256
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @ZackaryW on GitHub (Jul 27, 2022).
Original GitHub issue: https://github.com/brentvollebregt/auto-py-to-exe/issues/291
Originally assigned to: @ZackaryW on GitHub.
Quick Checks For You
Describe the bug
there should be an option to prevent moving completed folder to cwd or at least mitigate rewriting files if it already exists
my folder structure is
repo
i build the app using
One Directory, the folder is in use and it directly writes into my source codeExpected behavior
should never happen if the target fallback directory already has file
@brentvollebregt commented on GitHub (Jul 27, 2022):
If this application is writing into your "source code", I feel like you should move directories as this tool writes to "./output" by default - this is somewhere we definitely would not expect to see source code.
@ZackaryW commented on GitHub (Jul 27, 2022):
@brentvollebregt that is not the case,
the package is not named as
output, if one directory mode is selected and the utility detects the folder is currently in use, it will move itself to the os.cwd directory, which is the root directory of the repo, overwriting the source package folder with the output@ZackaryW commented on GitHub (Jul 27, 2022):
im explicitly referring to these instances
i expect them to be generated at
./outputbut they are moved to the root directory@brentvollebregt commented on GitHub (Jul 27, 2022):
I notice you output directory input is empty. Did the UI load like that or did you remove it?
I didn't see any details about clearing it in your reproduction steps so if you didn't clear it or override it, this is an issue.
@ZackaryW commented on GitHub (Jul 27, 2022):
i noticed just now that the output directory occasionally shows empty value after loading the config.
It seems to be a rare occasion
@brentvollebregt commented on GitHub (Jul 28, 2022):
Are you able to reproduce this consistently? If not, I won't be able to identify what's wrong.
@github-actions[bot] commented on GitHub (Sep 26, 2022):
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.
@github-actions[bot] commented on GitHub (Oct 1, 2022):
Closing issue due to no activity in more than 60 days.