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 might a
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/
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
On Tue, Feb 7, 2017 at 7:32 AM, Simon McVittie wrote:
> This is not portable to platforms that don't have symlinks (hello Windows)
FYI, Windows has symlinks:
https://msdn.microsoft.com/en-us/library/windows/desktop/aa363878(v=vs.85).aspx
https://en.wikipedia.org/wiki/NTFS_symbolic_link
--
bye,
On Mon, 06 Feb 2017 at 16:43:32 -0500, Thomas Nyberg wrote:
> What I would ideally like is for the module
> code to be put somewhere off the regular system path and then have the
> binary "know" how to find it.
If you do this:
/usr/
├── bin/
│ └── script → ../share/mypackage/scri
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
6 matches
Mail list logo
