The practice is to have the scripts in /usr/bin and the setuptools provide a nice simple way to make this happen. I have also seen packages where the executable was in the sit-packages directory and then a link to it is created in /usr/bin. I do not like this second approach as it creates extra stuff one has to remember and care for when the package is created.

Also the unqualified import assumes that python forever more will keep . on the load path. This may not be the case and then one has to fiddle with the path in the script, also bad practice. Importing from the new python package is a safe and commonly accepted best practice.

If at all possible it would be nice to keep this.