On Thursday, May 14, 2015 06:55:40 AM Tristan Seligmann wrote:
On 14 May 2015 at 06:04, Scott Kitterman deb...@kitterman.com wrote:
Why can't python-cryptography use python-ipaddr that's already in the
archive?
cryptography is python2/3 dual-source. Carrying a Debian-specific
patch[1
On Thursday, May 14, 2015 05:42:56 AM Tristan Seligmann wrote:
Package: wnpp
Severity: wishlist
Owner: Tristan Seligmann mithra...@mithrandi.net
* Package name: python-ipaddress
Version : 1.0.7
Upstream Author : Philipp Hagemeister
* URL :
On Tuesday, May 05, 2015 11:34:46 PM Jeremy Lainé wrote:
Hi Stefano,
Thanks for taking on the svn - git migration. From a practical point
of view: where should we commit new changes? Is the migration considered
done, or should we still commit to SVN?
This was a sample migration. Still
On Friday, May 01, 2015 10:37:08 PM Barry Warsaw wrote:
On Apr 30, 2015, at 12:46 AM, Stefano Rivera wrote:
Here's where I currently am (a migration of r32486):
https://anonscm.debian.org/cgit/python-modules/svn-migration/
I did a quick test of converting one of these repos to git-dpm.
I
On Friday, May 01, 2015 01:28:43 PM Luca Falavigna wrote:
2015-04-26 18:26 GMT+02:00 Luca Falavigna dktrkr...@debian.org:
Would it be better to start filing a MBF against the affected packages
Is there consensus about this MBF? I'd like to work on it on the
coming days, so please express
On Saturday, April 25, 2015 03:42:29 PM Tomasz Buchert wrote:
Hi guys,
I'm preparing a package for this library:
https://bitbucket.org/bgneal/enigma/ It's rather trivial (see
alioth:/git/collab-maint/python-enigma.git), but I have two questions that
remain:
* the library provides a
On Thursday, April 23, 2015 02:52:33 PM Enrico Zini wrote:
On Mon, Apr 20, 2015 at 11:14:28AM -0400, Paul Tagliamonte wrote:
So, round one of all of this is getting the critical path *under* each
of our services ready, so that when we need to migrate, we don't need
to scramble.
There is
On Monday, April 20, 2015 12:04:14 PM Enrico Zini wrote:
HOWEVER. I am the only person currently looking after all that code, and
my development time on it is mostly spent fixing bugs and implementing
the features that make it useful. See for example [1] and [2] for the
kind of things that are
On Thursday, April 16, 2015 06:45:08 PM Stefano Rivera wrote:
Hi Scott (2015.04.15_18:30:23_+0200)
If we are sharing dist-packages, then pypy can probably use the same
binary when the content would be the same. Only in cases where the
content is different would you duplicate a separate
On Wednesday, April 15, 2015 04:54:45 PM Stefano Rivera wrote:
Hi Scott (2015.04.15_02:17:18_+0200)
Consensus seems to be give it a shot and try to see what works.
There are no pypy apps, so this isn't an issue yet.
What is the it that's to be given a shot? I see two choices there?
On April 15, 2015 11:17:52 AM EDT, Stefano Rivera stefa...@debian.org wrote:
Hi Scott (2015.04.15_02:17:18_+0200)
Upstream Python's direction for Python paths is in favor of
explicitly
numbered
/usr/bin/python2 and /usr/bin/python3. In support of this, rough
consensus in
the room is that
On April 15, 2015 11:24:30 AM EDT, Stefano Rivera stefa...@debian.org wrote:
Hi Scott (2015.04.15_17:19:39_+0200)
Since these pypy extension packages are new and there are no
applications, I
think it would make a lot of sense to limit this to PY3. It makes
things much
simpler technically.
On Wednesday, April 15, 2015 02:16:58 PM Barry Warsaw wrote:
On Apr 15, 2015, at 12:24 PM, Scott Kitterman wrote:
Maybe I'll mellow over time, but currently my thinking is that if there's
an upload to point /usr/bin/python at a python3, it will be immediately
followed by one where I remove
On Wednesday, April 15, 2015 04:27:51 PM Paul Tagliamonte wrote:
Heyya d-p,
I'd like to send an email to d-d-a asking that project to consider no
longer creating new Debian tools in Python 2.
I'd like this to have the endorsement of the team, so, does anyone object to
me asking people to
On Wednesday, April 15, 2015 11:00:53 PM Stefano Rivera wrote:
Hi Scott (2015.04.15_22:42:26_+0200)
P.S. It would be nice if there would be a PEP that says to never ever do
this. I know it would make Arch have a sad, but they'll get over it.
I think everyone wants to make Arch sad. In
On Wednesday, April 15, 2015 11:07:13 PM Matthias Klose wrote:
On 04/15/2015 10:27 PM, Paul Tagliamonte wrote:
Heyya d-p,
I'd like to send an email to d-d-a asking that project to consider no
longer creating new Debian tools in Python 2.
I'd like this to have the endorsement of the
of Python installed, 'python' refers to that whether it
is Python 3 or 2. So it's already not a safe assumption that 'python'
always means Python 2, even if you discount Arch.
On 15 April 2015 at 21:04, Scott Kitterman skl...@kitterman.com wrote:
On April 15, 2015 8:00:22 PM EDT, Barry Warsaw ba
On April 14, 2015 6:01:56 PM EDT, Paul Tagliamonte paul...@debian.org wrote:
=== BITS FROM THE DEBIAN PYCON HANGOUT ===
Agenda:
- Discuss how we might support multiple interpreters with Python 3
packages, for cpython + pypy C extensions.
- Set up a plan for
On Tuesday, April 14, 2015 09:22:22 AM Thomas Kluyver wrote:
On 14 April 2015 at 08:57, Scott Kitterman deb...@kitterman.com wrote:
I have scripts I use locally that are untouched in almost a decade that
use
/usr/bin/python.
I'm thinking about scripts that are written and distributed
On Tuesday, April 14, 2015 08:10:49 AM Barry Warsaw wrote:
On Apr 14, 2015, at 12:38 AM, Scott Kitterman wrote:
If you want python (which include /usr/bin/python), install it. If you
want python3, then the interpreter you're looking for is found at
/usr/bin/python3.
I just don't want
On Tuesday, April 14, 2015 08:24:01 AM Thomas Kluyver wrote:
On 14 April 2015 at 08:10, Barry Warsaw ba...@python.org wrote:
But it fails unhelpfully when you use it in a shebang.
$ /tmp/foo.py
bash: /tmp/foo.py: /usr/bin/python: bad interpreter: No such file or
directory
Let's
On April 13, 2015 4:30:59 PM EDT, Barry Warsaw ba...@debian.org wrote:
On Apr 13, 2015, at 10:17 PM, Stefano Rivera wrote:
Matthias and I are planning to have a Debian Python BoF at PyCon,
tomorrow afternoon. I think lunch is 2pm, so 3pm?
Meet outside the cPython sprint room?
+1; +1
Matthias
On Tuesday, April 14, 2015 01:57:26 AM Matthias Klose wrote:
On 04/14/2015 01:20 AM, Scott Kitterman wrote:
What is a /usr/bin/python launcher?
#! /bin/sh
python=$(shuffle /usr/bin/python2 /usr/bin/python3)
exec $python $@
I agree it's not perfect, there should be a preference depending
On Monday, April 13, 2015 10:36:43 PM Barry Warsaw wrote:
On Apr 14, 2015, at 01:57 AM, Matthias Klose wrote:
#! /bin/sh
python=$(shuffle /usr/bin/python2 /usr/bin/python3)
exec $python $@
That was more or less the joke I made at the Pycon Language Summit. It's
too twisted *not* to
On Wednesday, February 25, 2015 04:37:53 PM Barry Warsaw wrote:
Debian bug #744145 (Ubuntu LP: #1363642) describes this failure:
$ pip install --user --upgrade requests
$ pip install --user --upgrade mistunes
(well, any package will have the same effect for step #2)
Quick recap:
On February 11, 2015 10:04:50 AM EST, Michael Crusoe michael.cru...@gmail.com
wrote:
Hello,
I'm working on the packaging of the khmer project[0] with the
debian-med
team[1] and we've run into an odd problem: dh_python2 renames the
Python
extension shared library from `_khmermodule.so` to a
for the bug report, the diagnosis, and
+ the initial version of the patch
+- Note: Change is done inline to avoid adding a patch system during
+ freeze, so it does not appear in the DPMT svn
+
+ -- Scott Kitterman sc...@kitterman.com Sun, 23 Nov 2014 20:34:20 -0500
+
python-gnutls (2.0.1
+ fine patches, but the one used was the smaller change since Debian is in
+ pre-release freeze
+
+ -- Scott Kitterman sc...@kitterman.com Sun, 23 Nov 2014 21:51:06 -0500
+
pisa (3.0.32-1) unstable; urgency=low
* Initial release (Closes: #504277). Thanks to Toby Smithe
diff -u pisa
On October 16, 2014 5:49:37 PM EDT, Per Andersson avtob...@gmail.com wrote:
Hi!
A while ago I uploaded python-pies to the archive, a dependency
for frosted which is also in the archive.
One of the binary packages python-pies2overrides, has an
important bug; it overwrites configparser.py, which
On October 12, 2014 2:49:47 AM EDT, Thomas Goirand z...@debian.org wrote:
On 10/10/2014 12:59 PM, Ben Finney wrote:
Scott Kitterman deb...@kitterman.com writes:
Changing the number of commits is solving the wrong problem. The
problem that needs to be solved is including upstream commits
On October 9, 2014 5:36:02 AM EDT, Raphael Hertzog hert...@debian.org wrote:
On Thu, 09 Oct 2014, W. Martin Borgert wrote:
On 2014-10-09 10:02, Raphael Hertzog wrote:
I fixed the default configuration in setup-repository to limit to
20
commits per push as a maximum. And I also limited the
On October 9, 2014 10:43:38 AM EDT, Barry Warsaw ba...@debian.org wrote:
On Oct 09, 2014, at 10:19 AM, Scott Kitterman wrote:
Upstream commits are off topic.
Agreed. There's no reason why we need notifications of upstream
commits,
though I don't know if it's possible to filter them out.
I'm
On Friday, October 10, 2014 00:22:42 Dimitri John Ledkov wrote:
On 9 October 2014 20:57, Scott Kitterman deb...@kitterman.com wrote:
On October 9, 2014 10:43:38 AM EDT, Barry Warsaw ba...@debian.org wrote:
On Oct 09, 2014, at 10:19 AM, Scott Kitterman wrote:
Upstream commits are off topic
On Friday, October 10, 2014 11:08:53 Chow Loong Jin wrote:
On Thu, Oct 09, 2014 at 07:57:48PM -0400, Scott Kitterman wrote:
[..]
Presumably one is the one who set up the git repos. I, for another one,
would really appreciate it if someone would take care of this.
Don't they all share
On Friday, October 10, 2014 12:56:41 Charles Plessy wrote:
Le Thu, Oct 09, 2014 at 11:41:47PM -0400, Scott Kitterman a écrit :
On Friday, October 10, 2014 11:08:53 Chow Loong Jin wrote:
On Thu, Oct 09, 2014 at 07:57:48PM -0400, Scott Kitterman wrote:
[..]
Presumably one is the one
On September 23, 2014 6:46:58 PM EDT, Charles Plessy ple...@debian.org wrote:
Le Tue, Sep 23, 2014 at 10:29:10PM +0100, Sandro Tosi a écrit :
Hi all,
there's some people who's subscribed to the commit ml, so getting all
the changes done to our repos. Now, with the transition to git we are
On Thursday, September 04, 2014 15:40:42 Barry Warsaw wrote:
That gets you a source package, but the binary package FTBFS because one
additional test cannot be run during the build process (there's a DEP-8 test
for full coverage). Now though, you *must* commit or stash the d/changelog
change.
On Thursday, September 04, 2014 16:05:53 Scott Kitterman wrote:
On Thursday, September 04, 2014 15:40:42 Barry Warsaw wrote:
That gets you a source package, but the binary package FTBFS because one
additional test cannot be run during the build process (there's a DEP-8
test for full
On Saturday, August 30, 2014 09:44:30 Barry Warsaw wrote:
On Aug 30, 2014, at 11:19 AM, Simon McVittie wrote:
On 30/08/14 10:50, Cornelius Kölbel wrote:
But now my originial program package is empty and does not contain the
python code.
It looks like only the .install scripts are run, but
On August 30, 2014 1:06:41 PM EDT, Barry Warsaw ba...@debian.org wrote:
On Aug 30, 2014, at 12:57 PM, Scott Kitterman wrote:
I don't think that's the case for multiple binary packages.
Hmm. An example is enum34, which has python-enum34, python3-enum34,
and
python-enum34-doc binary packages. I
On Sunday, August 03, 2014 22:01:00 Dmitry Shachnev wrote:
On Sun, Aug 3, 2014 at 7:06 PM, Barry Warsaw ba...@debian.org wrote:
On Aug 02, 2014, at 06:23 PM, Scott Kitterman wrote:
If someone on the team is interested in this package staying in Debian and
willing to be added to uploaders
On Tuesday, August 05, 2014 11:54:37 Ben Finney wrote:
Vincent Cheng vch...@debian.org writes:
[…] just don't pick a source package name that's already taken, and
pick one that is relevant to your package […]
I further advise: Try to avoid names which are too broad (e.g.
“coverage” for a
On Saturday, August 02, 2014 17:09:55 Scott Kitterman wrote:
Package: ftp.debian.org
Severity: normal
Both of the human maintainers/uploaders of gnupginterface are retired. See
#698274 and #729385, leaving only the Debian Python Modules Team as an
uploader. The package has gone almost 5
Package: lintian
Version: 2.5.25
Severity: wishlist
For applications that use python-qt4, pyqtconfig has been the standard way to
access attributes about the PyQt4 installation. Upstream has decided to drop
this for alternate methodes. For now, we can continue to use the upstream
legacy
On July 13, 2014 6:00:58 AM EDT, Thomas Goirand z...@debian.org wrote:
Hi,
There's more and more packages in Sid which requires python-wheel. I
was
wondering if it was possible to do a backport of it. It seems very
likely, because the setup.py is handling old stuff like Python prior
2.7. Many
On July 14, 2014 1:35:51 AM EDT, Thomas Goirand z...@debian.org wrote:
On 07/13/2014 07:08 PM, Scott Kitterman wrote:
On July 13, 2014 6:00:58 AM EDT, Thomas Goirand z...@debian.org
wrote:
Hi,
There's more and more packages in Sid which requires python-wheel. I
was
wondering
python3.3 will be gone from Unstable as of the next dinstall.
Thanks for everyone that helped out.
Scott K
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
This isn't necessarily fatal. See python-dnspython (provides the dns module)
and python-dns (provides the DNS module). Sine python-captcha is already
used, I'd recommend picking an alternate name for your package. Since python
module names are case sensitive, this thing can happen and we
On June 2, 2014 3:06:15 PM MDT, Matt Grant m...@mattgrant.net.nz wrote:
Hi Torsten!
I can get an NMU for PyParsing done as I am a DPMT member. Any
Objections on the list?
Regards,
Matt Grant
On Mon, 2014-06-02 at 21:28 +0200, Torsten Marek wrote:
I'm sorry but I'm not active in Debian any
On May 29, 2014 7:54:53 PM EDT, Barry Warsaw ba...@debian.org wrote:
I'm looking again at updating tox to the latest upstream 1.7.1. Along
the
way, I'd like to make /usr/bin/tox a Python 3 script.
This requires that virtualenv be importable, e.g. `$python -m
virtualenv`. It
is today in Python 2
On May 29, 2014 8:27:07 PM EDT, Donald Stufft don...@stufft.io wrote:
On May 29, 2014, at 8:15 PM, Scott Kitterman deb...@kitterman.com
wrote:
On May 29, 2014 7:54:53 PM EDT, Barry Warsaw ba...@debian.org
wrote:
I'm looking again at updating tox to the latest upstream 1.7.1.
Along
the
way
The release team gave the go ahead today to make 3.4 the default, so that's
done. There are a few binNMUs to do (See #746709 for details).
Is anyone aware of anything that would prevent dropping python3.3 from
supported versions as soon as this transition is done?
Scott K
signature.asc
On May 19, 2014 9:55:22 AM EDT, Barry Warsaw ba...@debian.org wrote:
On May 19, 2014, at 12:19 PM, Piotr Ożarowski wrote:
...
* I don't think we should force maintainers to do changes in their
packages if it's not really needed,
(not to mention additional work for ftpmasters)
The additional
On Friday, May 16, 2014 11:28:45 Barry Warsaw wrote:
Here is the diff I propose to Debian Python policy, describing our policy on
packaging wheels.
Cheers,
-Barry
=== modified file 'debian/python-policy.sgml'
--- debian/python-policy.sgml 2014-05-12 10:21:25 +
+++
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,11 @@
nameScott Kitterman/name
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 wheels
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
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 a
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 x...@debian.org wrote:
On 30 April 2014 18:01, Matthias Klose d...@debian.org 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:
On April 30, 2014 11:31:55 AM EDT, Luca Falavigna dktrkr...@debian.org 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
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. This
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've
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 3.4
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. Ive accepted your request.
Welcome,
Scott K
signature.asc
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 unless
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 other
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, just run
Ben Finney ben+deb...@benfinney.id.au wrote:
Dmitry Shachnev mity...@gmail.com 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
On Friday, September 20, 2013 15:44:05 Thomas Kluyver wrote:
On 20 September 2013 12:08, Paul Tagliamonte paul...@debian.org 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
Paul Tagliamonte paul...@debian.org 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
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
Paul Tagliamonte paul...@debian.org 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
Paul Wise p...@debian.org 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
DDs and are part
Paul Tagliamonte paul...@debian.org 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
Paul Tagliamonte paul...@debian.org 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
paul...@debian.org wrote:
4) Python modules from dpkg are borderline useless for
developers. We
package modules so that
Kerrick Staley kerr...@kerrickstaley.com 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
On Sunday, September 15, 2013 14:34:27 Scott Kitterman wrote:
Kerrick Staley kerr...@kerrickstaley.com 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
Kerrick Staley kerr...@kerrickstaley.com 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
On Sat, Sep 14, 2013 at 9:25 AM, Scott Kitterman
deb...@kitterman.comwrote:
Kerrick Staley kerr...@kerrickstaley.com 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 Staley kerr...@kerrickstaley.com 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 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 a
Stefano Rivera stefa...@debian.org 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
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
default.
These issues
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
On Tuesday, July 30, 2013 16:15:58 Brian May wrote:
On 30 July 2013 15:52, Scott Kitterman deb...@kitterman.com 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 was based
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?
Scott
On Tuesday, July 30, 2013 11:19:58 Brian May wrote:
On 30 July 2013 11:15, Scott Kitterman deb...@kitterman.com 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.debian.org/viewvc
Jakub Wilk jw...@debian.org wrote:
* Barry Warsaw ba...@debian.org, 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.
Barry Warsaw ba...@debian.org wrote:
On Jul 24, 2013, at 01:32 PM, Scott Kitterman wrote:
Jakub Wilk jw...@debian.org wrote:
* Barry Warsaw ba...@debian.org, 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
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 wink. But the responses I've
read so far make me think I probably wasn't clear in what I am proposing.
On Jul
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:
Here's a further update on packages
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 to have no rule, IMO.
Rules for packaging things are normally
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, #710545, now
builds for all python3
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 K
I don't think they are enough
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 upstream
On Friday, June 28, 2013 09:08:33 PM Jakub Wilk wrote:
* Barry Warsaw ba...@debian.org, 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
On Sunday, June 23, 2013 07:21:53 PM Jakub Wilk wrote:
* Etienne Millon etienne.mil...@gmail.com, 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.
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 unrepoducible
pyepr builds successfully
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
401 - 500 of 683 matches
Mail list logo
