dgw
@elad661 That's why it would be enabled by a config flag.
Or just `sopel --restart` when #1333 is merged in? I'm not against adding a new command-line flag, either. Maybe Sopel could support a `--watch` mode that watches modules for changes...
Mm, implementing this was predicated on fixing the issues with reloading. And we've had this discussion several times now—we can't properly fix reloading until we _at minimum_ no longer support...
Agreed with @Exirel. We'll leave this for after we drop old Python versions, in 8.0, when we'll have guaranteed access to some better reloading machinery from more recent Pythons.
I imagine this still would be useful while prototyping stuff. Not everyone starts right in on a full package with tests when creating a new plugin. We'll likely never eliminate...
I already have to maintain localization files through Crowdin for another project, and am not interested in doing so for Sopel. If there was a way to let others maintain...
Calling it a wishlist item.
That'd be cool. I'm not clear on how this works with packaged installs vs. being installed from Git, because the version appears based on commit SHAs, but also haven't read...
What I'd _like_ is a way to load only the config sections of plugins, but (correct me if I'm forgetting something) that's not possible with the current loader architecture, plugin...
This should have been dropped back to draft status weeks ago. Or really, about 5 months back.