Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.maint.python > #9230

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

Show all headers | View raw

[Multipart message — attachments visible in raw view] - view raw

On Tue, Feb 07, 2017 at 08:50:02AM -0500, Thomas Nyberg wrote:
> 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 so if I start a normal interpreter
> `import offlineimap` does work (which I'd rather it not). Am I completely
> missing something here or did you possibly mean another example package?
You should look at the sid package version, it's different there.

-- 
WBR, wRAR

Back to linux.debian.maint.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

Re: Best way to package a python module which is "private" with  exposed calling script Thomas Nyberg <tomuxiong@gmx.com> - 2017-02-07 15:00 +0100
  Re: Best way to package a python module which is "private" with  exposed calling script Andrey Rahmatullin <wrar@debian.org> - 2017-02-07 15:20 +0100
    Re: Best way to package a python module which is "private" with  exposed calling script Thomas Nyberg <tomuxiong@gmx.com> - 2017-02-07 18:50 +0100

csiph-web