Hi,
Am 16.04.2016 um 18:15 schrieb Leo Famulari:
>/Can you look at the 'python-wrapper' package and see if it would solve/
>/this problem for you?/
This solves the problem only party: When adding "python-wrapped" as a
native-input to some module you need to explicitly *remove* it for
"package-wi
Am 16.04.2016 um 18:15 schrieb Leo Famulari:
> Can you look at the 'python-wrapper' package and see if it would solve
> this problem for you?
Thanks for the pointer. I'll try it out and report. Will take few days
unfortunately.
--
Regards
Hartmut Goebel
| Hartmut Goebel | h.goe...@craz
On Sat, Apr 16, 2016 at 04:42:15PM +0200, Hartmut Goebel wrote:
> Hi,
>
> I'm stepping into problems packaging python modules again and again
> since Python 3.4 is not available as `python`. Same for pip, and other
> binaries in the python-3 package.
Can you look at the 'python-wrapper' package
Hi,
I'm stepping into problems packaging python modules again and again
since Python 3.4 is not available as `python`. Same for pip, and other
binaries in the python-3 package.
I propose
a) for python 3: adding symlinks from the unversioned binary name (e.b.
python) to the versioned
ones (e.g
