Jokosher extensions should not end in .py or .egg
Bug #76684 reported by
Brent Core
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Jokosher |
Confirmed
|
Low
|
Unassigned |
Bug Description
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.
To post a comment you must log in.
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.