Problem with new location of scripts

[felixdivo]

Calling: python -m can.logger does not seem to work on the develop branch? I have to use the full path: python -m can.scripts.logger.

Reported by @Lauszus over here.

[felixdivo]

Also need to consider newly added script from #390.

[felixdivo]

Okay, I can confirm it. The problem seems that python can only import real modules (with an real own file) but not the "virtual" modules create by the __init__.pys. I guess, we we have two options:

1. someone knows how to properly run these "virtual" modules
2. go back to the old way of doing this: Simply put the modules it into the top level folder (python-can/can/the_script_is_here.py
3. keep it like this, this would be a cleaner structure, but would be backwards incompatible and a bit more to type for the user
4. make another small file in the top level folder (python-can/can/this_location.py and call the can.scripts.some_script from there

@christiansandberg What do you think?

[felixdivo]

(Note for myself: TODO: Update setup.cfg.)

[felixdivo]

I added some regression tests to branch python-can/fix_scripts, and will merge it together with the fix of this issue once we decide what to do.

[christiansandberg]

I would prioritize user interface and external API over internal structure, but that's just my opinion. I didn't see the way it was before as a big issue.

[felixdivo]

Well, I guess you're right. Im my opinion it was confusing for people new to the codebase, but that's just how it is now. I'll revert the relevant changes. -.-