Conversation

Notices

1. Embed this notice
   Glyph (glyph@mastodon.social)'s status on Monday, 10-Mar-2025 01:54:27 JST Glyph

   pro tip: do you want to edit a #Python script which:

   1. can only ever be a script
   2. should never be imported as a module
   3. you want to be recognized by your editor as a python file without faffing around with extra hints
   4. for whatever reason you don't want to have a __main__ block?

   don't make it a .py file, make it a .pyw file.

   • Embed this notice
     Glyph (glyph@mastodon.social)'s status on Monday, 10-Mar-2025 01:54:26 JST Glyph

     in reply to

     The official purpose for these is that on Windows they will suppress the console window that comes up when you double-click on a .py file to run it, but it generally works well as a secondary file extension for your top-level code, particularly for GUI apps: https://docs.python.org/3/tutorial/appendix.html#executable-python-scripts

     Blaise Pabón - controlpl4n3 repeated this.
   • Embed this notice
     Glyph (glyph@mastodon.social)'s status on Monday, 10-Mar-2025 01:54:26 JST Glyph

     in reply to

     I've had this thought rattling around in my brain for a while and I *just* got around to doing this today. My particular use-case is that I want a script file with the basename root "Pomodouroboros" because py2app takes the app name from the script name. But having a directory with "Pomodouroboros.py" in it where the main package is called pomodouroboros/__init__.py causes all kinds of minor headaches. Just renamed all my main scripts and it seems to work great: https://github.com/glyph/Pomodouroboros/commit/54042517a1bd2597b9aa5033f0ee23163593c861