Jokosher extensions should not end in .py or .egg

[Brent Core]

If extensions end in .py or .egg, then this will confuse users who may have other files on their system that end in .py. They may try to load it into Jokosher, causing untold mayhem. I like how Jokosher projects end in .jokosher, giving the user an actual semblance of what the file is used for and what program uses it. Maybe extensions should end in .jextension or jokostension or jokostend? Just anything but .py.

[Laszlo Pandy (laszlok)]

I agree that importing a random .py file into Jokosher could be pretty bad, but do we really want to require distros to recognize every single mime-type we throw at them? Should we really be encouraging the proliferation of ultra-specific mime types like .jextension or .jpresets, etc? Maybe we could make these files just use a generic ending like .xml or something.

[Brent Core (brentcore2)]

agreed. .xml sounds like a good idea. Maybe there could be some kind of (sorta) security mechanism to prevent non-Jokosher-related .py files from running in the extensions manager? Like just a quick variable check in the code before loading it? Granted, it's not really "security" but at least it would prevent a user from accidentally ruining something by haphazardly loading some python code.

[John Green (john-thegreens)]

Hmm I see the problem here. The extension module being imported has to satisfy quite rigorous checks to see that it is a valid extension. However to do this it has to first be imported. And if, instead of being an importable module, it is ,say , a script then this means it gets executed. Maybe we need some sanity checking like the variable check you mention before we import.

We looked at using a different extension name but the egg system doesn't like being called anything other than .egg