[GH-ISSUE #544] .py file browse does not working as expected #415

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

Originally created by @mcagriaksoy on GitHub (Oct 15, 2025).
Original GitHub issue: https://github.com/brentvollebregt/auto-py-to-exe/issues/544

Originally assigned to: @brentvollebregt on GitHub.

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

While using the WSL i have seen a problem, when I enter the "Script Location" for the file, the file browser cannot filters the .py files correctly on my wsl-ubuntu system. It filters other files without any problem, like .json, .icon and so on. I will share problematic one and the one without any error below:

Problematic file browser UI:
Image

Without any problem:
Image

As you can see even there is a .py file exist on the path, it cannot be displayed.

To Reproduce
Steps to reproduce the behavior (install dependencies, do this in the auto-py-to-exe UI):

Open app on wsl-ubuntu, try to import .py file and observe that the file browser ui cannot filter the files correctly.

Expected behavior

.py files should be visible.

Originally created by @mcagriaksoy on GitHub (Oct 15, 2025). Original GitHub issue: https://github.com/brentvollebregt/auto-py-to-exe/issues/544 Originally assigned to: @brentvollebregt on GitHub. **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** While using the WSL i have seen a problem, when I enter the "Script Location" for the file, the file browser cannot filters the .py files correctly on my wsl-ubuntu system. It filters other files without any problem, like .json, .icon and so on. I will share problematic one and the one without any error below: Problematic file browser UI: <img width="660" height="478" alt="Image" src="https://github.com/user-attachments/assets/51920311-2635-4450-86fc-9b8041fdab1e" /> Without any problem: <img width="656" height="420" alt="Image" src="https://github.com/user-attachments/assets/ccdc5a3d-3905-4410-b5ea-1ca907833d79" /> As you can see even there is a .py file exist on the path, it cannot be displayed. **To Reproduce** _Steps to reproduce the behavior (install dependencies, do this in the auto-py-to-exe UI):_ Open app on wsl-ubuntu, try to import .py file and observe that the file browser ui cannot filter the files correctly. **Expected behavior** .py files should be visible.
kerem 2026-02-26 12:21:31 +03:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@brentvollebregt commented on GitHub (Oct 16, 2025):

Nice spot, thanks for raising this. I wonder if it's the ; in "*.py;*.pyw" - the other cases do not have this,

github.com/brentvollebregt/auto-py-to-exe@4792d9a2cd/auto_py_to_exe/dialogs.py (L39)

<!-- gh-comment-id:3409224616 --> @brentvollebregt commented on GitHub (Oct 16, 2025): Nice spot, thanks for raising this. I wonder if it's the `;` in `"*.py;*.pyw"` - the other cases do not have this, https://github.com/brentvollebregt/auto-py-to-exe/blob/4792d9a2cd46f79dfe52e3b631b4c9f4bfbf6b76/auto_py_to_exe/dialogs.py#L39
Author
Owner

@brentvollebregt commented on GitHub (Oct 16, 2025):

Looking at other usages on GitHub, file_types = [("Python files", "*.py *.pyw"), ("All files", "*")] may fix this

<!-- gh-comment-id:3409233976 --> @brentvollebregt commented on GitHub (Oct 16, 2025): Looking at other usages on GitHub, `file_types = [("Python files", "*.py *.pyw"), ("All files", "*")]` may fix this
Author
Owner

@mcagriaksoy commented on GitHub (Oct 16, 2025):

Yes @brentvollebregt I tested, your proposed solution fixes the problem. I`ll create PR.

<!-- gh-comment-id:3410298324 --> @mcagriaksoy commented on GitHub (Oct 16, 2025): Yes @brentvollebregt I tested, your proposed solution fixes the problem. I`ll create PR.
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#415
No description provided.