Hi Paul (2012.04.18_22:09:35_+0200)
Nobody thinks python3 is important enough to have a debhelper infrastructure?
The solution to that is multibuild, it just isn't ready yet.
When it is, I think it's safe to assume that debhelper will learn how to
drive it, pretty quickly.
It'll also improve a
On Thursday, April 12, 2012 08:30:41 AM Barry Warsaw wrote:
Hi Paul,
On Apr 12, 2012, at 02:09 AM, Paul Elliott wrote:
A recent review of my package asked me to consider making a python3
version.
Excellent! One more down the road to Python 3 world domination. :)
But the response below
Hi Paul (2012.04.18_10:09:30_+0200)
I am not a expert python packager. I am dubious about a bunch of cargo cult
packagers all writing seperate but similar debian/rules complications.
Indeed, it's messy and far from ideal.
Why can not some expert that really know what she is doing write the
[Paul Elliott, 2012-04-18]
I am not a expert python packager. I am dubious about a bunch of cargo cult
packagers all writing seperate but similar debian/rules complications.
It seems like one is creating a lot of debugging/maintainance problems.
Why can not some expert that really know
On Apr 18, 2012, at 03:09 AM, Paul Elliott wrote:
I am not a expert python packager. I am dubious about a bunch of cargo cult
packagers all writing seperate but similar debian/rules complications.
That's why I wrote the style guide; hopefully at least we'll converge on one
set of
On Wednesday, April 18, 2012 10:12:24 AM Barry Warsaw wrote:
On Apr 18, 2012, at 03:09 AM, Paul Elliott wrote:
I am not a expert python packager. I am dubious about a bunch of cargo
cult packagers all writing seperate but similar debian/rules
complications.
That's why I wrote the style
On Wednesday, April 18, 2012 10:35:04 AM Paul Elliott wrote:
On Wednesday, April 18, 2012 10:12:24 AM Barry Warsaw wrote:
On Apr 18, 2012, at 03:09 AM, Paul Elliott wrote:
I am not a expert python packager. I am dubious about a bunch of cargo
cult packagers all writing seperate but similar
On Wednesday, April 18, 2012 02:35:20 PM Paul Elliott wrote:
On Wednesday, April 18, 2012 10:49:34 AM Scott Kitterman wrote:
Alternately you could invest a little time in understanding what Barry's
written up and build both sets of binaries from one source. This is the
usual method.
The
On Wednesday, April 18, 2012 02:46:33 PM Scott Kitterman wrote:
No. You'd need overrides for a python3 only source package as well. The
fundamental problem is debhelper doesn't know about building for python3.
That doesn't change no matter how many source packages you split it up
into.
On Wednesday, April 18, 2012 03:09:35 PM Paul Elliott wrote:
On Wednesday, April 18, 2012 02:46:33 PM Scott Kitterman wrote:
No. You'd need overrides for a python3 only source package as well. The
fundamental problem is debhelper doesn't know about building for python3.
That doesn't
On Apr 18, 2012, at 03:09 PM, Paul Elliott wrote:
Nobody thinks python3 is important enough to have a debhelper infrastructure?
I wouldn't say that. I'd say that the higher level tools are simply lagging
behind demand. The low-level tools are available and won't significantly
change. As Scott
Hi Paul,
On Apr 12, 2012, at 02:09 AM, Paul Elliott wrote:
A recent review of my package asked me to consider making a python3 version.
Excellent! One more down the road to Python 3 world domination. :)
But the response below says that is difficult. It is several months old, has
this
On Thursday, April 12, 2012 08:30:41 AM Barry Warsaw wrote:
Hi Paul,
I'm not sure what you mean by no python3 program to test it. You can and
should create the Python 3 extension modules. `apt-get install python3`
should do the trick, right?
I mean that I have python 2 programs that use
On Apr 12, 2012, at 10:09 AM, Paul Elliott wrote:
On Thursday, April 12, 2012 08:30:41 AM Barry Warsaw wrote:
Hi Paul,
I'm not sure what you mean by no python3 program to test it. You can and
should create the Python 3 extension modules. `apt-get install python3`
should do the trick,
Hi Paul (2011.11.17_12:05:46_+0200)
I created a package with py2dsc. After some tweeks, it works correctly. The
upstream says package also works with python 3. How do I alter my source
package to also produce a python 3 version?
That's currently non-trivial, and certainly not in the realm of
On Thu, Nov 17, 2011 at 7:55 PM, Stefano Rivera wrote:
Hi Paul (2011.11.17_12:05:46_+0200)
I created a package with py2dsc. After some tweeks, it works correctly. The
upstream says package also works with python 3. How do I alter my source
package to also produce a python 3 version?
That's
Hi Paul (2011.11.17_15:17:07_+0200)
Would dh --with python2,python3 not work? I've seen that in some packages
IIRC.
No. That'll run dh_python2 dh_python3, but do nothing to build the
module for python3.
SR
--
Stefano Rivera
http://tumbleweed.org.za/
H: +27 21 465 6908 C: +27 72 419
On Nov 17, 2011, at 01:55 PM, Stefano Rivera wrote:
If you don't need the python3 version, yet, I'd ignore this until the
tools improve.
Piotr was working on a rewrite of python-multibuild at UDS in Orlando. I
haven't heard any status on that. Piotr, how's that going? Do you have
anything
[Barry Warsaw, 2011-11-17]
On Nov 17, 2011, at 01:55 PM, Stefano Rivera wrote:
If you don't need the python3 version, yet, I'd ignore this until the
tools improve.
Piotr was working on a rewrite of python-multibuild at UDS in Orlando. I
haven't heard any status on that. Piotr, how's
19 matches
Mail list logo
