debian-de...@liska.ath.cx wrote
>Jakub Wilk writes:
>> * Olе Streicher , 2012-07-10, 12:14:
>>>I: python-astropy: arch-dep-package-has-big-usr-share 4137kB 87%
>
>>> How do I create an arch independend package that contains these
>files?
>
>> [...] I'd rather not do that. You will likely end u
Toni Mueller wrote:
>
>Hi,
>
>On Mon, Jun 18, 2012 at 01:09:55PM +0200, Jakub Wilk wrote:
>> * Toni Mueller , 2012-06-18, 12:55:
>> >debian/control:
>> >...
>> >X-Python-Version: >= 2.5, << 2.8
>>
>> In any case, I'd get rid of the "<< 2.8" part. Surely roundup cannot
>> be incompatible with P
Yaroslav Halchenko wrote:
>
>On Tue, 12 Jun 2012, Denis Laxalde wrote:
>> >>Policy-compliant package name would be "python-numpydoc", but that
>> >>could be easily confused with "python-numpy-doc". So I agree with
>> >>your assessment: "python-numpydoc-sphinx" is a better for the
>binary
>> >>p
On Tuesday, June 12, 2012 02:13:14 PM nore...@alioth.debian.org wrote:
> I would like to join the python-apps team for the following reasons.
>
> * short term: take care of pdfposter, update it to version 0.5.0, try to
> close the existing bugs. * mid term: if the Maintainer of pdfposter
> continu
On Friday, June 01, 2012 01:52:09 AM Nicolas Dandrimont (dandrimont-guest)
wrote:
> Hello,
>
> I'd like to join the PAPT to adopt and maintain the hellanzb package, that I
> use and which needs some love.
>
> I'm a DM and already a member of DPMT.
>
> Thanks in advance,
> Nicolas
Welcome to
On Friday, May 18, 2012 11:48:07 AM Ana Guerrero wrote:
> Hi,
>
> I'm considering how feasible is removing Qt3 from wheezy. Even if
> we freeze soon, removing packages is never a problem :-)
>
> One of the big parts of the effort would be removing python-qt3, there are
> only 6 packages in the ar
On Wednesday, May 16, 2012 12:04:05 PM Johannes Ring wrote:
> [Cc'ing debian-python]
...
> @debian-python: Since DOLFIN does not work with Python 3 (yet) maybe a
> Build-Conflicts should be added? And what about X-Python-Version? This
> is currently set to ">= 2.5". Should it be ">= 2.5, << 3.0" or
On Saturday, May 12, 2012 09:46:55 AM Sandro Tosi wrote:
> On Fri, Apr 13, 2012 at 3:26 PM, Scott Kitterman
wrote:
> > On Friday, April 13, 2012 08:37:26 AM Sandro Tosi wrote:
> >> On Thu, Apr 12, 2012 at 23:35, Scott Kitterman
wrote:
> >> > On Thursday, April 12
On Friday, May 04, 2012 06:38:30 PM Dmitrijs Ledkovs wrote:
> On 04/05/12 18:23, Sandro Tosi wrote:
> > On Fri, May 4, 2012 at 7:19 PM, Jakub Wilk wrote:
> >>> or in setuptools.
> >>
> >> Ideally, by burning it with fire.
> >
> > CPython upstreams are developing a new module to replace distutils
On Tuesday, May 01, 2012 10:45:24 AM Barry Warsaw wrote:
...
> The ipaddr library is as well, though that might get the "provisional"
> tag.
...
This is one I'll need to keep an eye on as ipaddr is packaged in dpmt as a
seperate module (maintained by me). Upstream has a separate release that's
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 build
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
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
On Saturday, April 14, 2012 05:12:54 PM Paul Wise wrote:
> On Fri, Apr 13, 2012 at 9:26 PM, Scott Kitterman wrote:
> > times when the only 'solution' available is a short term hack that's
> > needed
> > for Ubuntu's time based release schedule that isn'
On Friday, April 13, 2012 08:37:26 AM Sandro Tosi wrote:
> On Thu, Apr 12, 2012 at 23:35, Scott Kitterman wrote:
> > On Thursday, April 12, 2012 11:04:33 PM Sandro Tosi wrote:
> >> On Thu, Apr 12, 2012 at 22:50, Scott Kitterman
wrote:
> >> > On Thursday, April 12
On Thursday, April 12, 2012 11:04:33 PM Sandro Tosi wrote:
> On Thu, Apr 12, 2012 at 22:50, Scott Kitterman wrote:
> > On Thursday, April 12, 2012 10:20:04 PM Sandro Tosi wrote:
> >> To give a (fresh) example and what I meant above, you can try to
> >> answer this provo
On Thursday, April 12, 2012 10:20:04 PM Sandro Tosi wrote:
> To give a (fresh) example and what I meant above, you can try to
> answer this provocative question: Why Ubuntu has Python 2.7.3 since
> more than 2 days (even before it was publicly announced) while Debian
> is still stuck with a RC, Fin
On Thursday, April 12, 2012 09:12:23 PM Sandro Tosi wrote:
> On Thu, Apr 12, 2012 at 16:13, Scott Kitterman wrote:
> > I don't think that the *-defaults packages and the interpreter packages
> > fundamentally require the same maintainer, but I expect it to be
> > pro
On Thursday, April 12, 2012 11:25:07 AM Stefano Zacchiroli wrote:
> On Tue, Apr 03, 2012 at 10:36:58AM +0200, Stefano Zacchiroli wrote:
> > Allow me be blunt then: do we have volunteers to maintain the pythonX.Y
> > packages? Can those volunteers manifest themselves on this list?
>
> So, ~10 days
On Tuesday, March 20, 2012 07:26:29 PM Geoffroy Youri Berret wrote:
> > Is Python 3.1 really not supported? I couldn't find any information
> > about this in upstream source. If it's really not, then you need a
> > version constraint for the build-dependency.
>
> Right, this is a mistake.
> I shou
On Monday, March 19, 2012 05:29:25 PM Jakub Wilk wrote:
> * Scott Kitterman , 2012-03-19, 09:29:
> >>>"The generated minumum dependency may be different than the lowest
> >>>version currently supported. In such cases, X-Python-Version must
> >>>still be
On Monday, March 19, 2012 12:20:18 PM Jakub Wilk wrote:
> * Scott Kitterman , 2012-03-17, 14:29:
> >Upon reflection, this could be better stated something like this:
> >
> >"The generated minumum dependency may be different than the lowest
> >version currently su
There are four packages that use X-P-V and current. This has never been
supported, so intead of silenting ignoring this, I'm going to (at some point)
turn this into an error. Here's the DD list:
Anton Gladky
gmsh (U)
Christophe Prud'homme
gmsh (U)
Christophe Trophime
gmsh (U)
Da
I didn't make a patch for this one as I don't have a firm proposal.
Currently Python policy says:
Lists of multiple individual versions (e.g. 2.4, 2.5, 2.6) work for `XS-
Python-Version' and will continue to be supported, but are not recommended and
will not be supported by `X-Python-Version' o
On Saturday, March 17, 2012 07:18:59 PM Jakub Wilk wrote:
> >The most common exception to this is architecture independent Python 3
> >modules with no version specific code. Since, unlike in Python,
> >version specific directories are not needed for Python 3, there is no
> >need to constrain th
I've attached a patch (it's built on the last one I sent) that attempts to
clarify policy around packages that only work with specific versions of
Python/Python3. Here's what I attempted to do:
- Changed should support the default version to should support all supported
versions.
- Dropped t
On Saturday, March 17, 2012 02:08:44 AM Scott Kitterman wrote:
> On Thursday, March 15, 2012 12:02:42 PM Scott Kitterman wrote:
> > Last night I uploaded an updated python3-defaults package to fix a
> > problem where dh_python3 was not honoring version requirements set the
> >
On Friday, March 16, 2012 07:20:34 PM Scott Kitterman wrote:
> When Squeeze was nearing freeze, the definition of some aspects of python3
> support were still new. There were some packages that used
> XS-Python-Version in debian control, instead of X-Python3-Version.
>
> There ar
On Thursday, March 15, 2012 12:02:42 PM Scott Kitterman wrote:
> Last night I uploaded an updated python3-defaults package to fix a problem
> where dh_python3 was not honoring version requirements set the -V option in
> debian/rules or X-Python3-Version in debian/control.
>
>
I've worked on a couple of dh_python3 bugs in the last few days and as a
result, gotten my hands dirty on the Python 3 dependency generation code.
This caused me to consider the question of specifying which Python 3 versions
are supported by a package a little more closely. I have generally con
When Squeeze was nearing freeze, the definition of some aspects of python3
support were still new. There were some packages that used XS-Python-Version
in debian control, instead of X-Python3-Version.
There are now none (one package still has it in debian/control, but it's not
actually used
Last night I uploaded an updated python3-defaults package to fix a problem
where dh_python3 was not honoring version requirements set the -V option in
debian/rules or X-Python3-Version in debian/control.
If you have a python3 module package that set a minumum version of python3 to
3.2 using o
Thomas Kluyver wrote:
>Sandro:
>> I won't migrate to dh_python2, so it would be a waste of your time.
>
>Why not? I thought python-support was deprecated, and everything was
>supposed to move to dh_python2?
>
>So, is it practical to usek dh_python3 for python 3 while keeping
>python-support for
On Wednesday, March 14, 2012 04:02:40 PM Simon McVittie wrote:
> On 14/03/12 15:40, Barry Warsaw wrote:
> > It would be nice to build for all supported Python 3 versions. Python
> > 3.3 is currently scheduled for August of this year, but I'm hoping
> > we'll start seeing it show up in Debian aroun
On Wednesday, March 14, 2012 12:41:32 PM Thomas Kluyver wrote:
> On 14 March 2012 04:13, Scott Kitterman wrote:
> > I did have to make some additional changes, such as using a policy
> > compliant
> > binary name in python3, as we did for PyQt4 (python3-pyqt4.qsci) and
>
On Tuesday, March 13, 2012 11:27:01 PM Thomas Kluyver wrote:
> Following on from tornado, the attached patch updates the packaging for
> qscintilla2 to build Python 3 bindings. It's roughly following the
> python-qt4 packaging (which it depends on).
I did have to make some additional changes, such
On Tuesday, March 13, 2012 11:27:01 PM Thomas Kluyver wrote:
> Following on from tornado, the attached patch updates the packaging for
> qscintilla2 to build Python 3 bindings. It's roughly following the
> python-qt4 packaging (which it depends on).
Except for the Python/Python 2 parts (it's a non
>From the discussion in Bug #662965:
> > ...packages sharing the same namespace must use the same helper.
>
> They can use different helpers if the package that is earlier in
> sys.path uses this trick:
>
> http://docs.python.org/library/pkgutil.html#pkgutil.extend_path
The multiple helper path
Arthur de Jong wrote:
>Hello lists,
>
>I've been seeing what it would take to remove python-central from my
>system and it wasn't actually that much so I sent patches to the BTS
>for
>the remaining packages and fixed a few python-apps-team and
>python-modules-team packages in SVN.
>
>The list o
On Sunday, January 29, 2012 12:28:22 AM Scott Kitterman wrote:
> I just uploaded a new python-qt4 revision to experimental (it's arrival will
> be delayed since it has to go through new.
>
> It is experimental for at least three reasons:
>
> 1. It is changed to build w
On Sunday, January 29, 2012 10:46:12 PM Piotr Ożarowski wrote:
> [Scott Kitterman, 2012-01-29]
>
> > 2. It builds a new python3-pyqt4-dbus (and dbg) package that needs
> > python3- dbus which is only available in experimental at the moment.
>
> why not python3-dbus.main
On Sunday, January 29, 2012 08:25:35 PM Simon McVittie wrote:
> On 29/01/12 05:28, Scott Kitterman wrote:
> > 2. It builds a new python3-pyqt4-dbus (and dbg) package that needs
> > python3- dbus which is only available in experimental at the moment.
>
> Thanks, I'd mea
"Piotr Ożarowski" wrote:
>[Scott Kitterman, 2012-01-29]
>> 2. It builds a new python3-pyqt4-dbus (and dbg) package that needs
>python3-
>> dbus which is only available in experimental at the moment.
>
>why not python3-dbus.mainloop.qt?
Because I didn&
I just uploaded a new python-qt4 revision to experimental (it's arrival will
be delayed since it has to go through new.
It is experimental for at least three reasons:
1. It is changed to build with a multiarched Qt as qt4-x11 4.8 in
experimental is.
2. It builds a new python3-pyqt4-dbus (and
On Thursday, January 26, 2012 05:06:20 PM Barry Warsaw wrote:
> I've had a few conversations about this between Scott and Jakub, but I think
> it's worth opening up to all of debian-python.
...
> 2) Add a quilt patch to comment out the distribute_setup lines above
...
I think my recommendation wou
We've had dh_sip now for a couple of years. Last year python3 packages were
added for sip4, but without the companion dh_sip3. I've now put it together
and it works ~like dh_sip.
For python3 packages that use sip, add the ${sip3:Depends} substitution
variable and at build time this will be
On Tuesday, January 17, 2012 07:14:23 PM Sandro Tosi wrote:
> On Tue, Jan 17, 2012 at 18:12, wrote:
> >Date: Tuesday, January 17, 2012 @ 17:12:00
> > Author: kitterman
> > Revision: 20032
> >
> > * Team upload
>
> ...
>
> > * Switch to dh_python2
>
> I think changing the python helper in
python-qt4 is currenlty broken in Unstable (See #653293) due to incompatible
changes in the new sip4 uploaded last week (thanks upstream). Upgrading
python-qt4 resolves this issue, but it is a major new release. I've rebuilt
some of the packages (like pykde4) the build-depend on it without iss
On Saturday, December 17, 2011 04:32:04 PM Julian Taylor wrote:
> On 12/14/2011 05:30 PM, Jameson Graef Rollins wrote:
> > On Wed, 14 Dec 2011 16:43:07 +0900, Arnaud Fontaine
wrote:
> >> About #651962, I guess that something like '<< 2.7' should be added
> >> to
> >> X-Python-Version...
> >
>
On 11/09/2011 06:45 AM, Jakub Wilk wrote:
* Piotr Ożarowski , 2011-11-08, 09:48:
doesn't dh_numpy do that already?
Yes it does, but as said above, the pydist file you want:
numpy_strict python-numpy-api$N, python-numpy (>= $foo)
doesn't contain "python-numpy-abi$N", so we should keep that
so
See #647210 for the most recent instance of these checks causing
problems. python-sip will raise a RuntimeError if the upstream version
of python-qt4 (specifically PyQt4.QtCore) used at runtime is different
than the one the package was built with.
RuntimeError: the PyQt4.QtCore module is vers
On 10/29/2011 05:23 PM, Bernd Zeimetz wrote:
On 10/29/2011 08:05 PM, Thomas Kluyver wrote:
Hi,
I've been having a go at repackaging some Python modules where I know the
same codebase can be compiled for Python 3. So far, that's pyzmq and
python-qt4. I've not done any packaging before, so I've n
On Thursday, October 06, 2011 08:50:30 PM Andrey Rahmatullin wrote:
> On Thu, Oct 06, 2011 at 04:12:44PM +0200, Thomas Waldmann wrote:
> > Considering that it'll take a while until wheezy gets stable, I hope
> > there is also a python 3.x (x=rather latest) then, so that projects can
> > do a python
On Monday, October 03, 2011 09:56:21 PM Jakub Wilk wrote:
> BTW, I'm slightly disturbed by the fact, that so many people believe
> that a Python helper does code inspection (or maybe use some magical
> means...) to generate python:Depends. It seems to be a new phenomenon, I
> don't recall any qu
On Sunday, October 02, 2011 09:38:37 PM Miguel Landaeta wrote:
> On Sat, Oct 1, 2011 at 9:25 AM, Thomas Waldmann wrote:
> > So, is anybody working on putting python2.7 into squeeze-backports or do
> > I need to work on that myself? (I don't have much experience with debian
> > packaging / policy,
On Tuesday, September 27, 2011 08:07:09 PM Luca Falavigna wrote:
> Il 27/09/2011 19:35, Scott Kitterman ha scritto:
> > We're currently looking into 642601.
>
> It seems some uploaders have been asked to provide an update. If they
> don't react, I could prepare a
The release team has given us a transition slot and python-defaults is ready
for upload, so we'll be starting the transition shortly. We're currently
looking into 642601. We're not aware of any other issues that might cause us
to delay.
Scott K
--
To UNSUBSCRIBE, email to debian-python-req
Currently python-qt4 is uninstallable due to breaks put in for python-dbus
when it switched. There's a proposed change to switch python-qt4 in DPMT svn.
Since switching sip4 to dh_python2 will break approximately the same packages
as switching python-qt4, I'm going to switch it too (working on
On Thursday, July 07, 2011 01:30:48 AM Scott Kitterman wrote:
> I've just uploaded 2.7.2-2 to experimental. It's mostly about dh_python2
> improvements from POX, but also has some minor updates to Python Policy
> that I think improve the currency of it a bit. Please review the
On Sunday, July 10, 2011 06:53:34 PM Jakub Wilk wrote:
> * Matthias Klose , 2011-07-10, 19:34:
> >Changes:
> > python-defaults (2.7.2-3) experimental; urgency=low
> > .
> >
> > * python: Provide python profiler.
> > * Provide a python2 symlink according to PEP 394.
>
> Excuse me, what? AFAICT
On Thursday, July 07, 2011 11:23:13 AM Brian Sutherland wrote:
> On Thu, Jul 07, 2011 at 09:18:19AM -0400, Scott Kitterman wrote:
> > On Thursday, July 07, 2011 04:27:32 AM Piotr Ożarowski wrote:
> > > [Scott Kitterman, 2011-07-07]
> > >
> > &g
On Thursday, July 07, 2011 08:43:29 AM Jakub Wilk wrote:
> * Scott Kitterman , 2011-07-07, 01:30:
> >I've just uploaded 2.7.2-2 to experimental. It's mostly about
> >dh_python2 improvements from POX, but also has some minor updates to
> >Python Policy that I think i
On Thursday, July 07, 2011 04:27:32 AM Piotr Ożarowski wrote:
> [Scott Kitterman, 2011-07-07]
>
> > B.Packaging Tools
> >
> > - B.1. distutils
> > - B.2. python-support
> > - B.3. python-central
> > - B.4.
46929 -0400
@@ -16,7 +16,7 @@
Scott Kitterman
- version 0.9.3.0
+ version 0.9.4.0
---
@@ -94,10 +94,11 @@
A.Build De
On Sunday, June 12, 2011 10:24:51 AM Yaroslav Halchenko wrote:
> On Sun, 12 Jun 2011, Tshepang Lekhonkhobe wrote:
> > > I am asking because I have a few packages which use pysupport now and
> > > it seems to work (so it is the mighty for me)... not sure if I am
> > > ready to invest time into doing
Nikolaus Rath wrote:
>Hello,
>
>What should I put into X-Python3-Version for a package that does not
>support Python 3? According to
>http://www.debian.org/doc/packaging-manuals/python-policy/ch-module_packages.html,
>not providing that header would mean that the package is compatible
>with
>all
Sandro Tosi wrote:
>On Mon, May 16, 2011 at 16:43, Scott Kitterman
>wrote:
>> I think it's deeply unfortunate that the pkgme authors chose
>duplicate
>> something for which there is already a reasonably complete solution
>rather
>> than focus on areas where
Sandro Tosi wrote:
>On Mon, May 16, 2011 at 16:43, Scott Kitterman
>wrote:
>> I think it's deeply unfortunate that the pkgme authors chose
>duplicate
>> something for which there is already a reasonably complete solution
>rather
>> than focus on areas where
Barry Warsaw wrote:
>On May 15, 2011, at 11:57 PM, Scott Kitterman wrote:
>
>>> http://pkgme.net/
>>
>>Which is rather less complete for Python packaging than stdeb and I'd
>prefer
>>we don't recommend.
>
>Perhaps, but I think it's a go
On Sunday, May 15, 2011 06:24:47 PM Barry Warsaw wrote:
> On May 15, 2011, at 10:40 PM, Piotr Ożarowski wrote:
> >[Janne Snabb, 2011-05-13]
> >
> >> I assume that "pypi-install" is the most sensible way to install
> >> Python packages which have not been packaged for Debian.
> >
> >true
> >
> >[...
On Wednesday, May 04, 2011 02:23:58 AM nore...@alioth.debian.org wrote:
> Johannes Ring has requested to join your project.
> Comments by the user:
> Hi,
>
> I am currently a member of the DPMT, but now I have started working on some
> packages that fits better under the umbrella of PAPT. Therefor
On Monday, May 02, 2011 04:18:57 AM Bernd Zeimetz wrote:
> On 04/29/2011 09:14 PM, Barry Warsaw wrote:
> > On Apr 28, 2011, at 02:41 PM, Bernd Zeimetz wrote:
> >> I can't see any problemswith pysupport here -
> >> http://wiki.debian.org/Python/PythonSupportToDHPython2
> >> The migration is well doc
Floris Bruynooghe wrote:
>On 22 April 2011 19:55, Stefano Rivera wrote:
>> Hi Barry (2011.04.22_03:28:12_+0200)
>>> When I click on 'last log' for say ia64, I just see a build log with
>>> no failures in it. So why does it show up on the main page with
>>> straight red-X's?
>>
>> The transition
Lars Wirzenius wrote:
>Hi,
>
>I'd like to join the DPMT. I'm going to be uploading my backup
>application (Obnam, http://braawi.org/obnam/) to Debian, and it has a
>number of dependencies on Python libraries, which I've also written.
>I'm
>starting with the dependencies.
>
>In order to have the p
On Thursday, April 21, 2011 09:28:12 PM Barry Warsaw wrote:
> On Apr 15, 2011, at 10:17 AM, Scott Kitterman wrote:
> >I just uploaded python-defaults to Unstable that drops Python 2.5 and adds
> >Python 2.7 as supports Python versions. Python-central, distribute, and
> >pyt
I just uploaded python-defaults to Unstable that drops Python 2.5 and adds
Python 2.7 as supports Python versions. Python-central, distribute, and
python-stdlib-extensions are already updated to support Python 2.7. The
planned python-support upload later today will complete having the core Pyt
The release team has ack'ed the python3 transition (See #617272). I'll upload
a new python3-defaults shortly. Once that's in we'll start with the required
sourceful uploads and binNMUs. Over the next few days, please keep an eye on
any python3 related uploads for unusual results. Since python
On Thursday, March 31, 2011 09:54:46 AM Barry Warsaw wrote:
> On Mar 30, 2011, at 04:02 PM, Piotr Ożarowski wrote:
> >FYI: I plan to upload python-sphinx, python-defaults (without Python
> >2.5, with Python 2.7) and python3-defaults (with Python 3.2 instead of
> >Python 3.2) tomorrow. Please report
A couple of days ago I updated python-defaults and today (it's still Thursday
in my mind because I haven't slept yet) I updated python3-defaults. Unstable
now how the latest dh_python2/dh_python3 and pycompile changes.
The only difference between Unstable and Experimental is which Python/Pyth
Most of you probably figured this out already from the cc: of 619487 to
debian-python, but just in case ...
dh_python2 dropped ${python:Breaks} - This means you should remove Breaks:
${python:Breaks} from packages as you update them. In the mean time, it's
presence is harmless so there's no ne
On Thursday, March 24, 2011 09:35:21 am Stefano Rivera wrote:
> I see we still suggest ${python:Provides}. I was encouraged in
> #debian-python to never use these unless there's an existing
> dependency on a versioned package name.
>
> There are no real packages using a name like python2.X-modulen
On Friday, March 18, 2011 10:23:05 pm Scott Kitterman wrote:
> Today's mail on XB-Python-Version motivates me to send out an overdue call
> for inputs on further changes to the Python policy. I know that needs to
> go.
>
> What else needs doing?
>
> Personally I'd
Today's mail on XB-Python-Version motivates me to send out an overdue call for
inputs on further changes to the Python policy. I know that needs to go.
What else needs doing?
Personally I'd like to concentrate on getting policy for Python 3 to the point
that it's possible to produce a correct
Floris Bruynooghe wrote:
Hi The wiki page at http://wiki.debian.org/Python/PyCentral2DhPython2 tells you
to remove the XB-Python-Version lines in debian/control but the python policy
still says they are required in section 2.3. I presume this is outdated in the
policy? If so any reason why thi
On Thursday, March 10, 2011 06:15:01 am Raphael Hertzog wrote:
> On Thu, 10 Mar 2011, Piotr Ożarowski wrote:
> > seriously, THERE WILL BE NO NEW PYTHON 2.X VERSION RELEASED UPSTREAM¹,
> > we don't have to worry about 2.X transitions when 2.7 will become the
> > only supported one. If you don't like
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
It looks like we are ready to switch the default python3 in Unstable from 3.1
to 3.2. It should affect a relatively small number of packages.
Source uploads needed:
distribute pyt
On Sunday, March 06, 2011 03:02:25 pm Yaroslav Halchenko wrote:
> On Sun, 06 Mar 2011, Scott Kitterman wrote:
> > One thing that is a clear advantage for bzr is that it supports both a
> > traditional centralized workflow and modern DVCS workflow so that not
> > everyone
Robert Collins wrote:
>On Mon, Mar 7, 2011 at 7:52 AM, Scott Kitterman
>wrote:
>...
>> reasonably comfortable for both. It's not as fast a git and it
>suffers from
>> not being able to do partial checkouts (like git), so it's very much
>a middle
>> g
On Sunday, March 06, 2011 12:43:23 pm Sandro Tosi wrote:
> On Sun, Mar 6, 2011 at 17:33, Barry Warsaw wrote:
> > Is this a Debian-wide decision, or can each subteam go its own way?
>
> each team can decide on its own, but git is very wide accepted within
> Debian, which is to be considered when c
On Friday, March 04, 2011 08:06:55 pm Jakub Wilk wrote:
> * Piotr Ożarowski , 2011-03-05, 01:39:
> >>>dh_python2 and dh_python3 cannot be used for the same files at the
> >>>same time (that's why dh_python2 igores python3-* packages, that's
> >>>why dh_python3 ignores python-* packages and that's w
"Piotr Ożarowski" wrote:
any objections to change all shebangs (that do not match
/usr/bin/python\d(\.\d+) but do math .+python.* regexp) to /usr/bin/python¹ in
dh_python2 and to /usr/bin/python3 in dh_python3? (+ an option to disable this
behaviour in both helpers) if yes, should options (-OO
On Friday, March 04, 2011 01:23:40 pm Barry Warsaw wrote:
> So I know many of you are on python-dev, so you might have seen this come
> up, but traffic there can be pretty heavy at times.
>
> Upstream Python recommends that the shebang line for scripts should be
>
> #!/usr/bin/env python
>
> how
On Friday, March 04, 2011 08:30:02 am ProgVal wrote:
> Hello,
>
> Python 2.7 is available in the Experimental repository, and I use it as the
> default Python interpreter.
> All modules and software I use works Python 2.7, but, modules and libraries
> installed with aptitude are installed for Pyth
On Tuesday, February 22, 2011 09:58:36 am Bernd Zeimetz wrote:
> On 02/22/2011 03:47 PM, Barry Warsaw wrote:
> > It would be nice if dh auto-detected a setup.py (and/or missing Makefile)
> > and didn't run 'make test' in that case, so that the
> > override_dh_auto_test wasn't necessary. Yah, I sho
On Tuesday, February 15, 2011 08:12:37 am Picca Frédéric-Emmanuel wrote:
> Le Mon, 14 Feb 2011 17:40:59 +0100,
>
> Picca Frédéric-Emmanuel a
écrit :
> > Hello,
> > I am working on a packqge which use PyQt4, but When I try to test it
> > I got this error message.
> >
> > picca@grisette:~/Debian/
"Andrey Rahmatullin" wrote:
>On Fri, Jan 21, 2011 at 01:08:34AM +0100, Jakub Wilk wrote:
>> >How about supporting both python (default being Python 2.7) and
>python3
>> >(default being Python 3.x, x=2 in Wheezy?) forever as two separate
>> >languages?
>> That's the plan. Except maybe "forever"
On Friday, October 15, 2010 05:45:24 pm Piotr Ożarowski wrote:
> FYI: [I already mentioned that on #debian-python and in other places,
> but it deserves a mail to debian-python as well]
>
> I think that we should support Python 2.7 and Python 3.2 only in Wheezy.
>
> Python 2.7 is the last version
On Saturday, August 14, 2010 03:09:35 am Sandro Tosi wrote:
> Hello,
> there was a BoF[1] about the plans for python in squeeze+1 but no
> minutes was sent to the list: 8 days are passed, so we have waited
> (while others, like perl team, sent it moments after the bof).
>
> [1] http://penta.debcon
On Friday, August 13, 2010 05:42:35 pm Jakub Wilk wrote:
> * Scott Kitterman , 2010-08-13, 17:32:
> >IMO the essential thing for Squeeze was getting X-P-V and X3-P-V
> >supported.
>
> Well, but python-support, the most widely used helper, doesn't support
> X-P-V. So
On Friday, August 13, 2010 04:58:37 pm Sandro Tosi wrote:
> Hello,
>
> On Fri, Aug 13, 2010 at 22:47, Scott Kitterman wrote:
> > On Friday, August 13, 2010 11:10:04 am Scott Kitterman wrote:
> >> http://paste.debian.net/83034/ captures what I think are the essential
601 - 700 of 772 matches
Mail list logo
