Re: Best way to package a python module which is "private" with exposed calling script

On 02/07/2017 08:54 AM, Andrey Rahmatullin wrote: On Tue, Feb 07, 2017 at 08:50:02AM -0500, Thomas Nyberg wrote: You should look at the sid package version, it's different there. Thanks a lot! (Should have been an obvious first step...) And thanks a lot everyone else! Also I figure I

Re: Best way to package a python module which is "private" with exposed calling script

Hi Simon, Thank you very much for the response! I've been looking at the offlineimap package on my system (jessie), but in my case `/usr/bin/offlineimap` is _not_ a symlink. Also the python code is not installed to `/usr/share/offlineimap` and instead to `/usr/share/pyshared/offlineimap/` and

Best way to package a python module which is "private" with exposed calling script

Hello, What I would like to do is to package a private python package without exposing it's internals. Here is the setup: * module - This is a module that contains the main code * script - This is a python script which handles some argument parsing stuff and then imports the module code to do