On Friday, May 16, 2014 14:09:26 Barry Warsaw wrote:
> Second draft.
> -Barry
>
> === modified file 'debian/python-policy.sgml'
> --- debian/python-policy.sgml 2014-05-12 10:21:25 +
> +++ debian/python-policy.sgml 2014-05-16 18:08:52 +
> @@ -32,7 +32,1
-05-12 10:21:25 +
> +++ debian/python-policy.sgml 2014-05-16 15:23:30 +
> @@ -32,7 +32,11 @@
> Scott Kitterman
> sc...@kitterman.com
>
> - version 0.9.5
> +
> +Barry Warsaw
> +ba...@debian.org
> +
> +
On Thursday, May 15, 2014 18:32:01 Barry Warsaw wrote:
> My thoughts...
>
> On May 16, 2014, at 12:07 AM, Matthias Klose wrote:
> > - should we add wheels everywhere? I don't think we should,
> >
> > but I'd like to state this somewhere, like in the python policy.
>
> Agreed, we should not add
Based on discussions with the release team, I think we'll be able to do this
next week (assuming the sip-api transition that just started goes well).
blender will need an upload and python-astropy is broken and will remain
broken until upstream fixes it. Are there any other issues people know o
On Wednesday, May 07, 2014 11:27:20 Barry Warsaw wrote:
> Should we also update Appendix B to promote --buildsystem=pybuild or at
> least reference it?
It's a reasonably safe bet that almost anything needs update.
Scott K
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with
On Monday, May 05, 2014 17:20:09 Paul Tagliamonte wrote:
> On Mon, May 05, 2014 at 09:18:57PM +, Tianon Gravi wrote:
> > Hi! :)
> >
> > I'm part of the docker-maint team (which is listed in Uploaders on
> > python-docker), and I'm interested in joining DPMT to help Paul maintain
> > and update
On April 30, 2014 1:15:42 PM EDT, Dimitri John Ledkov wrote:
>On 30 April 2014 18:01, Matthias Klose wrote:
>> Am 30.04.2014 17:31, schrieb Luca Falavigna:
>>> Hi,
>>>
>>> python-central is gone (\o/) and python-support usage is slowly
>>> decreasing in the archive:
>>> http://lintian.debian.org/
On April 30, 2014 11:31:55 AM EDT, Luca Falavigna wrote:
>Hi,
>
>python-central is gone (\o/) and python-support usage is slowly
>decreasing in the archive:
>http://lintian.debian.org/tags/dh_pysupport-is-obsolete.html
>
>Do you think it would be the right time to prepare a mass bug filing
>asking
On Sunday, March 30, 2014 17:01:05 Ben Finney wrote:
> Howdy all,
>
> I'm attempting to build a Python 3-only package, but ‘dh’ insists on
> trying to find some Python 2 versions.
>
> The ‘debian/control’ contains a “X-Python3-Versions” field, and does not
> contain any “X-Python-Versions” field.
On Tuesday, March 25, 2014 15:29:06 Barry Warsaw wrote:
> On Mar 25, 2014, at 03:19 PM, Donald Stufft wrote:
> >I assume once someone has installed pip with apt-get they’d still be able
> >to run pip install —upgrade pip if they wanted too?
>
> I would think they should be able to do that.
If I'v
On Wednesday, March 19, 2014 17:40:51 Barry Warsaw wrote:
> Signed by ba...@warsaw.us.Show Details
> TL;DR: Let's re-enable the ensurepip module in Python 3.4, and possibly
>address some usability issues. We should descend en masse on Montreal
> and stage a revolt at Pycon. :)
>
> Python
On Wednesday, March 05, 2014 18:28:56 Sandro Knauß wrote:
> Hello,
>
> I'm interested to join the team with my alioth account (hefee-guest). I want
> to package python-srs within this team. Scott K. has agreed to sponser me.
Sounds good. I"ve accepted your request.
Welcome,
Scott K
signature.
On Wednesday, January 08, 2014 23:22:40 Gudjon I. Gudjonsson wrote:
> Hi list
> I got a bug report regarding PyQwt (see below). Once again
> it segfaults and when I test PyQwt3d it segfaults as well.
>The problem is fixed by a new upload but my problem is that
> I cannot request a binNMU un
On Wednesday, October 30, 2013 09:57:36 Barry Warsaw wrote:
> On Oct 30, 2013, at 10:04 AM, Dmitry Shachnev wrote:
> >Not before python2.7 is removed from the archive. See previous
> >discussions on this ML, i.e. this thread:
> >http://lists.debian.org/debian-python/2013/07/msg00049.html.
>
> The
On Saturday, October 12, 2013 11:26:28 Thomas Goirand wrote:
> On 10/12/2013 01:26 AM, Barry Warsaw wrote:
> > On Oct 11, 2013, at 07:23 PM, Julian Taylor wrote:
> >> It is better if one disables internet access of package builds
> >> completely.
> >> With pbuilder and iptables this is very easy, j
Ben Finney wrote:
>Dmitry Shachnev writes:
>
>> In your particular case, python3-coverage depends on 'python3 (<<
>> 3.4), python3 (>= 3.3)', so when it is installed /usr/bin/python3
>will
>> be always a link to python3.3, so the shebang doesn't matter here.
>But
>> in general, I recommend peop
On Friday, September 20, 2013 15:44:05 Thomas Kluyver wrote:
> On 20 September 2013 12:08, Paul Tagliamonte wrote:
> > Don't take this as me trashing on Python or Pythonistas. If you want to
> > talk
> > about this in person, I'm usually at PyCon. I'm also usually in the
> > packaging
> > BOF. Per
Paul Tagliamonte wrote:
>On Wed, Sep 18, 2013 at 05:16:22PM +1000, Ben Finney wrote:
>> Howdy all,
>>
>> Over at the ‘python-dev’ forum, PEP 453 is being discussed. This
>affects
>> Debian packaging of Python, and packages written for Python.
>>
>> See the discussion thread and take the opport
On Monday, September 16, 2013 23:23:30 Kerrick Staley wrote:
> On Sun, Sep 15, 2013 at 11:34 AM, Scott Kitterman
wrote:
> > OK. I think that convinces me it's widely enough spread we ought to fix
> > this for Wheezy. I'll take it up with the release managers as it'
Paul Tagliamonte wrote:
>On Wed, Sep 18, 2013 at 10:57:30PM +0200, Tshepang Lekhonkhobe wrote:
>> On Wed, Sep 18, 2013 at 3:36 PM, Paul Tagliamonte
> wrote:
>> > 4) Python modules from dpkg are borderline useless for
>developers. We
>> > package modules so that apps can use them, not so t
Paul Tagliamonte wrote:
>On Wed, Sep 18, 2013 at 05:41:52PM +0200, Piotr Ożarowski wrote:
>> ok, I forgot to add ";)", but...
>
>Sure, but let's be more careful - I don't want people quoting "Debian
>Python" people telling people they're going to purge pip from the
>archive...
>
>It's all too of
Paul Wise wrote:
>On Wed, Sep 18, 2013 at 4:33 PM, Scott Kitterman wrote:
>
>> P.S. I'm not nominating myself to be the diplomat that talks to
>upstream for what are probably obvious reasons.
>
>Too late, upstream folks (for eg Barry Warsaw) are on this list, are
>D
Paul Tagliamonte wrote:
>On Wed, Sep 18, 2013 at 03:22:19PM +0200, Piotr Ożarowski wrote:
>> [W. Martin Borgert, 2013-09-18]
>> > As a passionate pip hater I would go for a Conflicts,
>> > which finally would make pip uninstallable :~)
>> > Next steps: get rid of gem, npm, EPT, ...
>>
>> +1 (un
On Wednesday, September 18, 2013 17:16:22 Ben Finney wrote:
> Howdy all,
>
> Over at the ‘python-dev’ forum, PEP 453 is being discussed. This affects
> Debian packaging of Python, and packages written for Python.
>
> See the discussion thread and take the opportunity to represent Debian
> https:/
On Sunday, September 15, 2013 14:34:27 Scott Kitterman wrote:
> Kerrick Staley wrote:
> >Scott, I booted up a CentOS 6.4 VM, and the symlink is there (runs
> >python2.6). I'd be interested to know if there are any other systems
> >where
> >it's unavailable th
Kerrick Staley wrote:
>Scott, I booted up a CentOS 6.4 VM, and the symlink is there (runs
>python2.6). I'd be interested to know if there are any other systems
>where
>it's unavailable though.
OK. I think that convinces me it's widely enough spread we ought to fix this
for Wheezy. I'll take i
2.7.
Scott K
>
>On Sat, Sep 14, 2013 at 9:25 AM, Scott Kitterman
>wrote:
>
>>
>>
>> Kerrick Staley wrote:
>> >Thanks!
>> >
>> >The upstream recommendation (from PEP 394 [1]) is that, going
>forward,
>> >portable scripts
Kerrick Staley wrote:
>Thanks!
>
>The upstream recommendation (from PEP 394 [1]) is that, going forward,
>portable scripts *can't* assume python is python2, and *should* use
>python2.
>
>- Kerrick
>
>[1] http://www.python.org/dev/peps/pep-0394/
I'm very familiar with it.
Now we get to Arch is
Kerrick Staley wrote:
>Please install /usr/bin/python2 as part of the default Debian install.
>It
>still doesn't exist on 7.1, which prevents scripts with a shebang of
>#!/usr/bin/python2 from running.
>
>Note that the following matters (which have derailed previous threads
>on
>this topic) are
On Wednesday, August 21, 2013 21:25:41 Diane Trout wrote:
> Hi,
>
> I wanted to help maintain python-lightblue which was currently up for
> adoption. I also submitted python-htseq a little while ago through the
> debian- med team.
>
> My day job is as a python programmer/systems administrator at
On Friday, August 02, 2013 09:13:56 Scott Kitterman wrote:
> python3.3 is the default python3. We're going straight to dropping
> python3.2 from supported python3 versions. binNMUs were already done for
> morse- simulator,postgresql-9.1,yafaray,and znc after python3.3 became
&g
Stefano Rivera wrote:
>Hi Dmitrijs (2013.08.05_00:05:50_+0200)
>> pypy published a release with python3 support
>
>I'm not entirely sure how to handle pypy3 yet...
>pypy3 will be able to share /usr/lib/python3/dist-packages, which
>probably means single binary packages for both cpython3 and
python3.3 is the default python3. We're going straight to dropping python3.2
from supported python3 versions. binNMUs were already done for morse-
simulator,postgresql-9.1,yafaray,and znc after python3.3 became default.
These issues still remain:
> libguestfs - No longer FTBFS on amd64, but do
On Tuesday, July 30, 2013 16:15:58 Brian May wrote:
> On 30 July 2013 15:52, Scott Kitterman wrote:
> > The package name is incorrect. Per the python policy, the binary name
> > should
> > be python-ajax-select. That's the module name.
>
> Really? I thought it w
On Tuesday, July 30, 2013 11:19:58 Brian May wrote:
> On 30 July 2013 11:15, Scott Kitterman wrote:
> > Where is the package?
>
> The source is on subversion:
>
> svn+ssh://
> svn.debian.org/svn/python-modules/packages/django-ajax-selects/trunk
> http://anonscm.debia
On Tuesday, July 30, 2013 09:37:21 Brian May wrote:
> > x: python-django-ajax-selects: incorrect-package-name python-ajax-select
>
> I don't know where it is getting the python-ajax-select name from.
>
> If I don't get any responses here, I will assume my package is fine.
Where is the package?
On Wednesday, July 24, 2013 07:09:26 PM Barry Warsaw wrote:
> Alright, I obviously haven't convinced anybody, so I'll drop it. We'll let
> the PEP 394 bug reports speak for themselves . But the responses I've
> read so far make me think I probably wasn't clear in what I am proposing.
> On Jul 25,
Barry Warsaw wrote:
>On Jul 24, 2013, at 01:32 PM, Scott Kitterman wrote:
>
>>Jakub Wilk wrote:
>>>* Barry Warsaw , 2013-07-24, 12:38:
>>>>In any case, it's come up that PEP 394 recommends distros start
>>>>adopting shebang lines that state /u
Jakub Wilk wrote:
>* Barry Warsaw , 2013-07-24, 12:38:
>>In any case, it's come up that PEP 394 recommends distros start
>>adopting shebang lines that state /usr/bin/python2 in their scripts,
>>and I don't think we do this yet. We should!
>
>We absolutely should not.
Definitely not. The ent
On Saturday, July 06, 2013 10:22:22 PM Scott Kitterman wrote:
> On Wednesday, July 03, 2013 01:55:07 PM Scott Kitterman wrote:
> > On Friday, June 21, 2013 01:30:00 AM Scott Kitterman wrote:
> > > On Wednesday, June 19, 2013 12:53:40 AM Scott Kitterman wrote:
> > > &
On Thursday, July 11, 2013 12:30:54 AM Stuart Prescott wrote:
> Thomas Goirand wrote:
> > On 07/08/2013 10:10 PM, Scott Kitterman wrote:
> >> There is no policy on this either way, so there's no "mistake".
> >
> > Well, the mistake is precisely t
On Monday, July 08, 2013 09:59:02 PM Thomas Goirand wrote:
> Hi,
>
> Over the last months, I've seen lots of inconsistency in the source
> package naming scheme in the python module maintained in the team.
> Sometimes, module X will have its source package called python-X or just X.
>
> If we hav
On Wednesday, July 03, 2013 01:55:07 PM Scott Kitterman wrote:
> On Friday, June 21, 2013 01:30:00 AM Scott Kitterman wrote:
> > On Wednesday, June 19, 2013 12:53:40 AM Scott Kitterman wrote:
> > > Here's a further update on packages pertaining to the 3.3 transition:
&g
On Wednesday, July 03, 2013 06:15:11 PM PICCA Frédéric-Emmanuel wrote:
> >Looking at where we are now, the open issues are down to #711761 and
> >#711761.
> To my opinion, (I am the maintainer of pytango) this is not a problem if
> pytango is not available on s390. I forwarded the bug to the upstre
On Wednesday, July 03, 2013 02:04:08 PM Barry Warsaw wrote:
> On Jul 03, 2013, at 01:55 PM, Scott Kitterman wrote:
> >Looking at where we are now, the open issues are down to #711761 and
> >#711761.
> Don't forget #711761 and #711761.
>
> :)
Meh. #710545.
Scott
On Friday, June 21, 2013 01:30:00 AM Scott Kitterman wrote:
> On Wednesday, June 19, 2013 12:53:40 AM Scott Kitterman wrote:
> > Here's a further update on packages pertaining to the 3.3 transition:
> >
> libguestfs - No longer FTBFS on amd64, but does on i386, #71054
On Friday, June 28, 2013 09:08:33 PM Jakub Wilk wrote:
> * Barry Warsaw , 2013-06-28, 11:46:
> >Could the project admins for DPMT and PAPT please add my non-guest
> >account?
>
> Done for DPMT.
Done for PAPT.
Scott K
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a su
On Sunday, June 23, 2013 07:21:53 PM Jakub Wilk wrote:
> * Etienne Millon , 2013-06-23, 14:57:
> >What is the preferred method: update the TODO page[2], post a RFS on
> >the list,
>
> I prefer e-mails, but I don't sponsor much, and other sponsors/reviewers
> preferences may vary.
>
> >or just set
On Friday, June 21, 2013 02:33:02 PM Mike Neish wrote:
> * Sandro Tosi, 2013-06-21, 08:37:
> > Sandro, are you okay with me adding Mike to the team, so the
> > he can commit the patch?
> >
> > sorry for the late reply; sure go ahead,
> >
> > Welcome to the team, Mike! :)
>
On Wednesday, June 19, 2013 12:53:40 AM Scott Kitterman wrote:
> Here's a further update on packages pertaining to the 3.3 transition:
>
> libguestfs - No longer FTBFS on amd64, but does on i386, #710545, now
> builds for all python3 versions
> nuitka FTBFS unrepod
On Wednesday, June 19, 2013 02:47:44 PM Brian May wrote:
> On 19 June 2013 14:33, Scott Kitterman wrote:
> > Patch to use the installed copy. I had to do this once before.
>
> How do I do this? I don't see any references to objects.inv in the
> upstream source code for
Here's a further update on packages pertaining to the 3.3 transition:
boost1.49 Fixed
flufl.bounce builds now that zope.interface is updated
hivex FTBFS fixed, dependencies fixed, nothing further to do.
libguestfs - No longer FTBFS on amd64, but does on i386, #710545, now builds
for all python3
On Wednesday, June 19, 2013 01:57:47 PM Brian May wrote:
> Hello,
>
> Can I please get somebody to review my django-tables package before I
> upload to Debian?
>
> I copied the updates from my django-filter package.
>
> Code is at
>
> http://anonscm.debian.org/viewvc/python-modules/packages/dja
On Wednesday, June 12, 2013 03:13:38 PM Scott Kitterman wrote:
> On Wednesday, June 12, 2013 12:48:45 AM Scott Kitterman wrote:
> > On Thursday, June 06, 2013 12:46:05 PM Scott Kitterman wrote:
> More updates and added all the "unknown" packages from the transition
> track
On Wednesday, June 12, 2013 12:48:45 AM Scott Kitterman wrote:
> On Thursday, June 06, 2013 12:46:05 PM Scott Kitterman wrote:
>
More updates and added all the "unknown" packages from the transition tracker.
Items marked as fixed in the last update have been removed.
>
>
On Thursday, June 06, 2013 12:46:05 PM Scott Kitterman wrote:
Here's another update based on work I've done, noticed other people did, or
responses to the last one of these I sent. It does not include work which I
neither notice nor people told me about. Items marked as fixed i
Vincent Bernat wrote:
>Hi!
>
>I just converted a package to add a Python3 package. I expected this to
>be as simple as:
>
> 1. Declaring the package in debian/control and add the appropriate
>dependency stuff.
> 2. Use dh --with python2,python3 $@.
>
>However, this is more tricky:
>
> - dh_
On Thursday, May 23, 2013 06:19:06 PM Scott Kitterman wrote:
> I've been working on this a bit ...
>
> On Tuesday, May 07, 2013 02:01:26 PM Jakub Wilk wrote:
> > python3-defaults maintainer(s?) decided to make python3.3 a supported
> > version without prior notice.
Jakub Wilk wrote:
>Quite a few packages carry Conflicts or Replaces with
>
>python2.4-MODULE or
>python2.3-MODULE or sometimes even
>pythonX.Y-MODULE for X.Y < 2.3.
>
>Not only such packages are long gone, but it's very unlikely that the
>file conflict that was the reason to add these Conflict
I've been working on this a bit ...
On Tuesday, May 07, 2013 02:01:26 PM Jakub Wilk wrote:
> python3-defaults maintainer(s?) decided to make python3.3 a supported
> version without prior notice. Yay. Now we have dozens of packages
> failing to build:
>
> boost1.49 FTBFS TODO
> boost1.50 FTBFS TOD
On Tuesday, May 21, 2013 11:05:30 PM Reuben Thomas wrote:
> Near the start of Chapter 1, Section 1.1:
>
> "implmentation" → "implementation"
>
> Checked against 0.9.4.2.
Fixed in the VCS for the next python-defaults upload.
Thanks,
Scott K
--
To UNSUBSCRIBE, email to debian-python-requ...@l
On Friday, May 17, 2013 02:13:10 PM Daniel Kahn Gillmor wrote:
> On 05/17/2013 01:55 PM, Scott Kitterman wrote:
> > You misunderstand.
>
> I don't think i misunderstood at all.
>
> > I'm all for having a good common environment for the team to work on. I
>
On Friday, May 17, 2013 01:50:09 PM Daniel Kahn Gillmor wrote:
> On 05/17/2013 01:40 PM, Scott Kitterman wrote:
> > If the team moves to full source git archives, I'll just drop the team
> > from
> > all the packages I maintain.
> >
> > Scott K
> >
On Friday, May 17, 2013 01:33:38 PM Daniel Kahn Gillmor wrote:
> On 05/17/2013 01:20 PM, Thomas Kluyver wrote:
> > This came up recently on debian-python. It's a very long thread, but the
> > basic outcome was that, while quite a few people wanted to move away from
> > svn, there was very little co
On Friday, May 17, 2013 10:53:39 AM Daniel Kahn Gillmor wrote:
> On 05/17/2013 08:22 AM, W. Martin Borgert wrote:
> > Quoting "Scott Kitterman" :
> >> Package: trac-accountmanager
> >
> > ...
> >
> >> Since the package has been removed fr
Do you object to the dropping of 2.6 or just the lack of discussion before it
was done?
Scott K
On Monday, May 06, 2013 09:29:11 AM Sandro Tosi wrote:
> Hello,
> has this been discussed *and* agreed on? I can only see Luca's mail
> for python plans, but no ack from other "members of the debian p
On Thursday, March 14, 2013 05:56:47 PM Dmitry Shachnev wrote:
> Hi,
>
> We discussed new lintian vcs-field-not-canonical check in IRC last week,
> which affects *lots* of packages in our SVN (see [¹]). Now people are
> recommended to use `svn://anonscm.debian.org/*` URIs instead of
> `svn://svn.d
On Saturday, February 23, 2013 12:24:16 AM Jakub Wilk wrote:
> * Scott Kitterman , 2013-02-22, 17:56:
> >>>>>>* you can ship extensions for more than one 3.x version in the
> >>>>>>same private directory, thanks to tags
> >>>>>
> &
Stefano Rivera wrote:
>Hi Scott (2013.02.23_00:17:30_+0200)
>> >> >* you can ship extensions for more than one 3.x version in the
>> >> >same private directory, thanks to tags
>> >> Does dh_python3 support such setup? (I would be very surprised if
>it
>> >> did.)
>> >You have a point. That'd be
Stefano Rivera wrote:
>Hi Jakub (2013.02.22_23:48:24_+0200)
>
>> * Stefano Rivera , 2013-02-22, 23:31:
>> >* you can ship extensions for more than one 3.x version in the
>> >same private directory, thanks to tags
>>
>> Does dh_python3 support such setup? (I would be very surprised if it
>> did
On Friday, February 22, 2013 03:14:30 PM Thomas Goirand wrote:
...
> The problem is that with SVN, it takes so much time and space
> (as each tag will generate some files), so you might have been
> fooled into thinking it would also with Git. But the reality simply
> not that at all.
...
I almost
On Thursday, February 21, 2013 02:02:09 PM Chow Loong Jin wrote:
> On 21/02/2013 12:46, Barry Warsaw wrote:
> > #9 on Steve Bennett's list is right on target IMHO, but I've had this
> > discussion so many times before, I don't have much energy for it again.
> >
> > """
> > 9. Git history is a bunc
On Thursday, February 21, 2013 01:52:59 PM Chow Loong Jin wrote:
> (Re-posted back on list. Sorry ScottK.)
>
> On 21/02/2013 12:37, Scott Kitterman wrote:
> > With git (I've never used gpb, and maybe that's my problem) I end up
> > having to do things like:
> >
On Thursday, February 21, 2013 03:00:56 PM Charles Plessy wrote:
> Le Wed, Feb 20, 2013 at 11:02:15PM -0500, Scott Kitterman a écrit :
> > On Thursday, February 21, 2013 11:08:13 AM Chow Loong Jin wrote:
> > ...
> >
> > > That argument applies to any VCS that
On Thursday, February 21, 2013 01:57:11 PM Thomas Goirand wrote:
> On 02/21/2013 12:32 PM, Barry Warsaw wrote:
> > On Feb 20, 2013, at 11:02 PM, Scott Kitterman wrote:
> >> It is to a degree, but the learning curve for git is subtantially steeper
> >> than for other
On Wednesday, February 20, 2013 11:46:31 PM Barry Warsaw wrote:
> >At least with git, you know when you've rewritten history -- you're no
> >longer on the same commit.
>
> #9 on Steve Bennett's list is right on target IMHO, but I've had this
> discussion so many times before, I don't have much ene
On Thursday, February 21, 2013 12:08:45 PM Chow Loong Jin wrote:
> On 21/02/2013 11:58, Scott Kitterman wrote:
> > On Thursday, February 21, 2013 11:12:58 AM Chow Loong Jin wrote:
> >> On 21/02/2013 01:59, Scott Kitterman wrote:
> >>> I've done the boring bits en
On Thursday, February 21, 2013 11:08:13 AM Chow Loong Jin wrote:
...
> That argument applies to any VCS that you don't use on a daily basis. You
> use bzr on a daily basis and forget how to use git. I use git on a daily
> basis and forget how to use svn/bzr and have to relearn it any time someone
>
On Thursday, February 21, 2013 11:12:58 AM Chow Loong Jin wrote:
> On 21/02/2013 01:59, Scott Kitterman wrote:
> > I've done the boring bits enough that my fingers mostly do them without
> > much attention from my brain. If I were going to abandon my current
> >
Thomas Goirand wrote:
>On 02/20/2013 11:45 PM, Scott Kitterman wrote:
>> On Wednesday, February 20, 2013 11:23:44 PM Thomas Goirand wrote:
>>> On 02/20/2013 10:43 PM, Scott Kitterman wrote:
>>>> First, full source repositories are much larger than debian only
>
On Wednesday, February 20, 2013 11:23:44 PM Thomas Goirand wrote:
> On 02/20/2013 10:43 PM, Scott Kitterman wrote:
> > First, full source repositories are much larger than debian only
> > repositories. I don't have a full checkout of all team packages locally,
> > so
On Wednesday, February 20, 2013 10:14:26 PM Thomas Goirand wrote:
> Upstream tarballs, in some cases, is a concept of the past. When
> they are released (sometimes, they simply don't exist), it may only
> an image based on a git tag. Then using Git tags is often better,
> because tags may be PGP si
On Wednesday, February 20, 2013 04:34:05 PM Thomas Goirand wrote:
> On 02/20/2013 12:41 PM, Scott Kitterman wrote:
> > This all seems to assume full source branches which is not something I'm
> > interested in participating in at all. I've tried it and I find it very
&
On Wednesday, February 20, 2013 12:23:02 PM Thomas Goirand wrote:
> On 02/20/2013 06:20 AM, Barry Warsaw wrote:
> > * Figure out whether full-source or debian/ only works better (maybe give
> > us>
> > both repos so we can play with them and discuss the pros and cons from
> > actual working ex
On Wednesday, February 20, 2013 12:23:02 PM Thomas Goirand wrote:
> The idea to use "git archive" was mostly from Julien Danjou. It's
> very nice because that way, we can use xz compression, instead
> of what upstream provides (that is, github .zip or .tar.gz, which
> isn't the best).
See devref 6
On Tuesday, February 19, 2013 05:20:48 PM Barry Warsaw wrote:
> On Feb 19, 2013, at 09:42 PM, Thomas Kluyver wrote:
> >After that it gets tricky, because we'd knock E out next, but the I'm not
> >sure where the votes counted for E (Scott & Barry) should be reallocated.
>
> If it makes things easie
On Sunday, February 17, 2013 10:35:01 AM Robert Collins wrote:
> On 17 February 2013 08:29, Dmitrijs Ledkovs wrote:
> > On 16 February 2013 14:27, Jakub Wilk wrote:
> >> * Scott Kitterman , 2013-02-16, 09:10:
> >>> On Saturday, February 16, 2013 12:43:02 PM Th
On Saturday, February 16, 2013 12:43:02 PM Thomas Kluyver wrote:
> On 16 February 2013 09:10, Thomas Goirand wrote:
> > It would be really stupid to only want to "claim" to be working as part
> > of the team, that's not at all what I want to do. I'd like to be able to
> > help when I can, and rece
On Thursday, February 14, 2013 04:53:23 PM Barry Warsaw wrote:
> On Feb 14, 2013, at 08:54 PM, Thomas Kluyver wrote:
> >I don't think it's a particularly good example, though. Lots of packages
> >continue to use the older helpers, and not due to a lack of time - attempts
> >to move away from the de
On Monday, February 11, 2013 05:05:23 PM Piotr Ożarowski wrote:
> [Barry Warsaw, 2013-02-11]
>
> > On Feb 11, 2013, at 03:51 PM, Piotr Ożarowski wrote:
> > >I'd also use python-pil and let python-imaging contain the compat code
> > >(with Depends: python-pil)
> >
> > Do you mean, get rid of the -
"Piotr Ożarowski" wrote:
>[Yaroslav Halchenko, 2013-01-20]
...
>> wouldn't it make more sense to ship it in a separate package since it
>is
>> relevant not only for python3? then it would also make possible to
>> provide backport packages
>
>yes, it makes sense. We already talked about it on I
I've just uploaded a version of python3-defaults to experimental to support
testing with python3.3 and with Piotr's new pybuild script (still definitely
experimental).
Here are the significant changelog entries:
* Add Python 3.3 to the list of supported Python 3 versions and make it a
def
On Friday, November 09, 2012 01:32:53 PM Thomas Kluyver wrote:
> On 9 November 2012 12:44, Maykel Moya wrote:
> > Even in the case of the more restrictive license applying only to
> > debian/* work? Could you/someone elaborate a little the implications of
> > this (link to fine documentation is we
Jakub Wilk wrote:
>* Raúl Benencia , 2012-10-15, 19:41:
>>I would very much like to join the Debian Python team. I've a bit of
>>experience packaging and programming python apps, and now I would like
>
>>to help with the maintainance of some of the team's packages.
>
>Welcome to the team! :)
>
n-qt4 (U)
Michael Meskes
pykde4 (U)
Miriam Ruiz
calibre
Modestas Vainius
pykde4 (U)
Python Applications Packaging Team
veusz
Scott Kitterman
python-qt4 (U)
qscintilla2 (U)
Sune Vuorela
pykde4 (U)
Torsten Marek
python-qt4 (U)
qscintilla2 (U)
signature.a
On Friday, September 28, 2012 09:53:42 AM Yaroslav Halchenko wrote:
> On Fri, 28 Sep 2012, Paul Wise wrote:
> > > ^^ this is a great idea. It'd be nice if we could prototype a flake8 /
> > > pyflakes run against the archive, and filter for serious errors
> >
> > We did do that at one point with py
On Monday, July 16, 2012 11:06:59 AM Yaroslav Halchenko wrote:
> On Mon, 16 Jul 2012, Scott Kitterman wrote:
> > OK. python-nipy depends on python-nipy-lib. Makes sense.
> >
> > Is python-nipy-lib useful on it's own?
>
> nope -- moreover it might be somew
On Monday, July 16, 2012 10:24:18 AM Yaroslav Halchenko wrote:
> On Mon, 16 Jul 2012, Scott Kitterman wrote:
> > >> 1. python{3}-foo which is arch all and follows the current naming
> > >
> > >convention
> > >
> > >> of foo being
Julien Cristau wrote:
>On Fri, Jul 13, 2012 at 11:57:01 -0400, Scott Kitterman wrote:
>
>> 1. python{3}-foo which is arch all and follows the current naming
>convention
>> of foo being the name you import. It would depend on the arch any
>python-foo-
>> ext pa
On Friday, July 13, 2012 11:48:57 AM Barry Warsaw wrote:
> On Jul 12, 2012, at 09:00 PM, Piotr Ożarowski wrote:
> >can we agree on a common suffix for such¹ packages and add a suggestion
> >to Debian Python Policy?
>
> +1
>
> >I use -ext (python-sqlalchemy-ext) but now I see that there are also
>
501 - 600 of 772 matches
Mail list logo
