* Ben Finney ben+deb...@benfinney.id.au, 2014-01-26, 17:06:
How can I convince ‘dh_python3’ to set the shebang to the *default*
Python 3 interpreter?
dh_python3 --shebang=/usr/bin/python3
(if I recall correctly)
--
Jakub Wilk
--
To UNSUBSCRIBE, email to
Jakub Wilk jw...@debian.org writes:
* Ben Finney ben+deb...@benfinney.id.au, 2014-01-26, 17:06:
How can I convince ‘dh_python3’ to set the shebang to the *default*
Python 3 interpreter?
dh_python3 --shebang=/usr/bin/python3
(if I recall correctly)
Thanks. So the manpage doesn't say,
Ben Finney ben+deb...@benfinney.id.au writes:
Thanks. So the manpage doesn't say, should I add that option for the
“build” action? The “install” action? Some other action? Reading the
source for ‘dh-python’ isn't very enlightening on this.
The manpage text “call dh_python3 in the binary-*
❦ 26 janvier 2014 02:49 CET, Thomas Goirand z...@debian.org :
Modules managed by python-support are installed in another directory
which is added to the sys.path using the .pth mechanism.
https://www.debian.org/doc/packaging-manuals/python-policy/ch-python.html#s-paths
Oh ok. Thanks!
Hi guys,
I am currently trying to package the ISMRMRD library (#732360), which
uses cmake for its build system and generates the c++ library and
corresponding Java and Python wrappers using SWIG.
I was wondering how that would play along with Debian packaging and what
would be the best approach
Python 3.4 beta2 is in testing, the python3-setuptools package is able to handle
3.4 builds. I am planning to go on with 3.4 as a supported Python 3 version
some time in February (targeting not later than Feb 9, release date of the first
3.4 release candidate). This should be doable without too
On Jan 26, 2014, at 10:19 AM, Jakub Wilk wrote:
* Ben Finney ben+deb...@benfinney.id.au, 2014-01-26, 17:06:
How can I convince ‘dh_python3’ to set the shebang to the *default* Python 3
interpreter?
dh_python3 --shebang=/usr/bin/python3
(if I recall correctly)
Should that be the default? There
On Jan 26, 2014, at 03:50 AM, Thomas Goirand wrote:
[1] https://wiki.debian.org/Python/TransitionToDHPython2 has:
The two traditionally popular Python helpers, python-support and
python-central have both been deprecated in favor of dh_python2.
So if someone do not agree with this, it should IMO
* Barry Warsaw ba...@debian.org [2014-01-26 13:24:38 -0800]:
I do think we should be switching all team maintained packages to dh_py2 and
finally getting rid of py-support and py-central (!). For the sake of
consistency, I'd love to see the latter two just disappear completely, but at
least
Nicolas Dandrimont ol...@debian.org writes:
- Dust off the team's PET instance ([1], which looks rather outdated).
[1] - http://python-modules.alioth.debian.org/cgi-bin/pet.cgi
I've never seen PET before. It seems redundant with the official QA
Packages Overview tool for each maintainer,
On Mon, Jan 27, 2014 at 7:37 AM, Ben Finney wrote:
Thanks for bringing PET to my attention. But I wonder whether it's
unused for good reason?
The only reason it is unused is people don't know about it or forget it exists.
What does PET do which the Packages Overview tool does not?
It looks
* Ben Finney ben+deb...@benfinney.id.au [2014-01-27 10:37:06 +1100]:
Nicolas Dandrimont ol...@debian.org writes:
- Dust off the team's PET instance ([1], which looks rather outdated).
[1] - http://python-modules.alioth.debian.org/cgi-bin/pet.cgi
I've never seen PET before. It seems
* Ben Finney ben+deb...@benfinney.id.au, 2014-01-26, 22:08:
How can I convince ‘dh_python3’ to set the shebang to the *default*
Python 3 interpreter?
dh_python3 --shebang=/usr/bin/python3
(if I recall correctly)
Thanks. So the manpage doesn't say, should I add that option for the
“build”
On Mon, Jan 27, 2014 at 12:14:12AM +0100, Nicolas Dandrimont wrote:
[ awesome points here ]
Cheers,
Nicolas Dandrimont
Hear, Hear!
Cheers,
Paul
--
.''`. Paul Tagliamonte paul...@debian.org | Proud Debian Developer
: :' : 4096R / 8F04 9AD8 2C92 066C 7352 D28A 7B58 5B30 807C 2A87
`.
Jakub Wilk jw...@debian.org writes:
You normally call dh_python3 in binary* targets. (Not sure if that's
what you're asking, though...)
It was, thank you.
There's --exclude option that looked promising to me, but it doesn't
seem to have any effect of shebang rewriting. :/
Darn. Well, that
On 26 Jan 2014 16:33, Paul Tagliamonte paul...@debian.org wrote:
On Mon, Jan 27, 2014 at 12:14:12AM +0100, Nicolas Dandrimont wrote:
[ awesome points here ]
Cheers,
Nicolas Dandrimont
Hear, Hear!
Ditto - I agree with just about everything Nicolas said. I'd love to see
this become a
Nicolas Dandrimont ol...@debian.org writes:
I am strongly of the opinion that the DPMT should be a team, not just
a SVN repository with random packages and a mailing-list where people
shout at each other when they dare touch those packages.
Thanks for expressing these constructive ideas.
On Sun, Jan 26, 2014 at 8:59 PM, Matthias Klose d...@debian.org wrote:
The 3.4 release is planned for March 16, so it shouldn't be too much of a
surprise to make 3.4 the default for the next Debian release, and hopefully be
able to drop 3.3.
\0/
--
To UNSUBSCRIBE, email to
18 matches
Mail list logo
