Yes, I’ve been thinking about this today too. In addition to raising the visibility on the web site, in the docs, etc. a couple initial options that come to mind are:
Move the demo folder to be a sub-package of the wx package, like
wx.demo, and add an entrypoint that will result in a launcher script like
Make the demo be a separately installable PyPI package, with a entrypoint like the above.
It’s less clear what to do about the current samples folder. Maybe make them launchable from the demo? Also, we’ve always said that the demo samples are intended to be editable and are to be experimented with, and that won’t be as easy if the files are buried in a
site-packages folder. It’s still possible with copy/paste from the editor tab in the demo, but then we’ll have more instances of confusion due to the missing
Anyway, food for thought.