Ethan Glasser-Camp writes:
> Hi guys,
>
> I asked on #debian-python a few days ago about the odds of Stackless
> being packaged. MadCoder, speaking unofficially, told me that this
> question would be better to ask on this list, and suggested I do some
> research about the compatibility between Sta
Manoj Srivastava writes:
> policy document. The current version, and future updates, are to be
> found at http://www.golden-gryphon.com/software/manoj-policy/
unreachable, comments for the posted text follow
> 1.1. Categorization of Python software
>
>Program/script
>
> Thi
Alexandre Fayolle writes:
> Hi,
> Am I expected to upload an unchanged 0.2.0-3 package so that it will get
> rebuilt with python2.4 as the default python version, or is something
> going to happen automatically, for instance a binary only NMU ?
a binaryNMU should be sufficient; if you know that th
With zope2.8 removed, the last package depending on python2.3 is gone,
so we are technically able to drop the support for python2.3. As
currently some packages have reverse dependencies on python2.3,
removing python2.3 without any other action, would open new RC reports
which doesn't seem to be ap
Thomas Bushnell BSG writes:
> On Wed, 2006-12-20 at 19:51 -0800, Steve Langasek wrote:
> > On Tue, Dec 19, 2006 at 11:17:03AM -0800, Thomas Bushnell BSG wrote:
> > > The python team has apparently decreed that python 2.3 will not be in
> > > etch. This forces every package to use the new version.
Alexandre Fayolle writes:
> On Tue, Jan 02, 2007 at 03:20:10PM +0100, Loïc Minier wrote:
> > Hi,
> >
> > On Tue, Jan 02, 2007, Tshepang Lekhonkhobe wrote:
> > > I tried to do some development using Etch's python2.5, but it fails to
> > > import pygtk and gtk modules and this is a regressio
Loïc Minier writes:
> On Tue, Jan 02, 2007, Pierre Habouzit wrote:
> > or do that "the clean way": edit /usr/share/python/debian_defaults
>
> This is slightly better indeed. My personal taste wouldn't allow me to
> edit a file under /usr, but I suppose a diversion would achieve a
> similar j
The current python2.4 and python2.5 package in testing and unstable
are ready for the transition to python 2.5 as the default python
version. However many packages still need updates for python 2.5,
either as a rebuild to build an extension module for 2.5, or to fix a
problem with python2.5. To ea
Ondrej Certik writes:
> On Dec 5, 2007 8:10 PM, Lucas Nussbaum <[EMAIL PROTECTED]> wrote:
> > On 05/12/07 at 13:37 +0100, Bernd Zeimetz wrote:
> > > >> 1. Why is there the build-conflict in the first place? This is the
> > > >> question to original maintainers (Marco, Alexandre, Jose, Matthias)
> >
Sanghyeon Seo writes:
> 2007/12/17, Tshepang Lekhonkhobe <[EMAIL PROTECTED]>:
> > > > Hi,
> > > > I was surprised to find python2.{4,5}-doc in contrib and wondered why?
> > > it needs latex2html to build.
> > Are there any free near-equivalents?
>
> There are, like hevea and tth, but as Python d
> From: =?utf-8?q?Adri=C3=A1n_Ribao_Mart=C3=ADnez?= <[EMAIL PROTECTED]>
> To: debian-python@lists.debian.org
> Subject: Debian 4.1 and Python 2.5
> Date: Wed, 13 Feb 2008 21:40:26 +0100
>
> Hello, I'd like to know if Python 2.5 will be the default version of python
> in Debian 4.1.
>
> Thank you.
Marc 'HE' Brockschmidt writes:
> Matthias Klose <[EMAIL PROTECTED]> writes:
> > Yes. If outstanding issues are solved; people want make you believe
> > that NMUs are enough to complete the transition. What needs to be
> > done:
> >
> > - Look for
Currently Debian's python has /usr/local/lib/python2.x/site-packages
in sys.path allowing for installation of local modules. Barry did
point out that this conflicts with a python installation, where
/usr/local is the default prefix, and the system python gets modules
from the local installation.
Ben Finney writes:
> Ben Finney <[EMAIL PROTECTED]> writes:
>
> > The Python distutils-sig group is currently discussing the topic of
> > package management, how setuptools interacts with package managers,
> > and what changes are desirable as a result.
> >
> > http://mid.gmane.org/[EMAIL PRO
Raphael Hertzog writes:
> On Tue, 15 Apr 2008, Adeodato Sim
Ondrej Certik writes:
> On Mon, Jul 7, 2008 at 2:12 PM, Matthias Klose <[EMAIL PROTECTED]> wrote:
> > Package: python-numpy
> > Version: 1:1.1.0-2
> > Severity: serious
> >
> > python-numpy now has an unconditional dependency on libatlas3gf-base,
> > n
[EMAIL PROTECTED] writes:
> On Mon, Jul 7, 2008 at 2:12 PM, Matthias Klose <[EMAIL PROTECTED]> wrote:
> > Package: python-numpy
> > Version: 1:1.1.0-2
> > Severity: serious
> >
> > python-numpy now has an unconditional dependency on libatlas3gf-base,
> &
> I'd be interested to know people's experiences with trying it out for
> packaging Python distributions for Debian.
how would it help? a Python distribution is a set of source/binary
packages which we do package separately.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsub
Bernd Zeimetz writes:
> Cyril Brulebois wrote:
> > Tristan Seligmann (20/12/2008):
> >> My personal preference ordering would probably be:
> >>
> >> hg, bzr, svn, git
> >
> > git, FD, *
>
> +1 :)
>
>
> http://whygitisbetterthanx.com
I only trust my own comparsion without any date and vers
Ondrej Certik schrieb:
> Hi,
>
> I finally packaged the newest uptream and committed all fixes into our
> svn repo for numpy. Kumar (or others), do you think you could please
> test the package?
numpy becomes big. see https://launchpad.net/bugs/309215. In the past the parts
depending on external
David Cournapeau schrieb:
> Hi,
>
> I am a developer of numpy and scipy, and I would be interested in
> helping numpy/scipy debian packages to be better on both Debian and
> Ubuntu. As a user of both Debian and Ubuntu, and one of the main
> developer working on build issues for numpy/scipy
while
Piotr Oz.arowski schrieb:
>> - 2.5 is superseded by 2.6; currently there doesn't seem to be
>>a reason to ship 2.5 and modules for 2.5 with the next stable
>>release. The upstream 2.5 maintainance branch doesn't see bug
>>fixes anymore, only security releases will be made from this
>>
Ondrej Certik schrieb:
> Hi Matthias,
>
> thanks for all the work you do. I have one question:
>
>> - 3.0/3.1: I do not plan to upload 3.0 to unstable or experimental,
>> but will prepare 3.1 packages for experimental and upload those
>> to unstable with the final release or a late release c
On 25.07.2009 05:47, Matthew Johnson wrote:
On Sat Jul 25 11:28, Mathieu Malaterre wrote:
On Fri, Jul 24, 2009 at 7:45 PM, Max Bowsher wrote:
...
It would be extremely nice too if all wrap language would adopt the
same convention. So that toolkit such as VTK/ITK/GDCM wrapping their
interface i
On 03.08.2009 19:16, Piotr Ożarowski wrote:
Just a follow-up the clear some things up:
* about the -common package (i.e. pysupport namespace issue):
- it's not a must, if one package can act as namespace provider,
there's no need to provide another one, of course,
- being able to list
On 02.07.2009 13:05, Jonas Meurer wrote:
On 23/06/2009 Fabio Tranchitella wrote:
Were you aware that we've renumbered the releases and inserted a less
ambitious Plone 4, which should be in beta by the end of the year? It
will run on (and require) Zope 2.12. Plone is finally joining the modern
P
On 20.09.2009 16:45, Jonas Meurer wrote:
if i got it right then packaging the dependencies as seperate packages
isn't an option for zope2.12, we'll have to include them within the
zope2.10 source tarball. the reason for that is, that zope2.12 requires
particular versions of the dependencies, and
Fyi, I replaced your NMU with my merge from Ubuntu, which already had these
changes. I may have missed the "indentation problems", please file separate bug
reports for these.
Matthias
On 03.11.2009 16:07, Piotr Ożarowski wrote:
Hi Matthias,
You uploaded new python-central package that fixe
On 15.01.2010 14:19, Luca Falavigna wrote:
* broken modules that use __file__ incorrectly will work without problems,
OK, I'd still warn loudly if that happens, though.
there are other cases where some modules/extensions do encode paths in generated
"config" files, like sip and the qt/kde bi
On 15.01.2010 14:27, Jakub Wilk wrote:
* Piotr Ożarowski , 2010-01-15, 11:58:
* maintainer script will byte compile .pyc files for all provided
symlinks / private directories if given Python version is installed
(dpkg -L output will be used to detect which files need byte compilation,
directorie
On 15.01.2010 11:58, Piotr Ożarowski wrote:
* no need for helper in Depends and Build-Depends - I want dh_python and
pycompile/pyclean to be shipped in python packages,
agreed. once these helper tools are mature for unstable/experimental, please add
yourself as an uploader to python-default
On 28.01.2010 12:50, Cyril Brulebois wrote:
Scott Kitterman (17/12/2009):
I believe that we are getting close to uploading Python 2.6 to
Unstable and dropping Python 2.4 as a supported Python version. If
we finish preparations in the next week, are there any ongoing
transitions a python2.6/pyt
On 23.03.2010 21:21, Jonathan Wiltshire wrote:
Hi,
Do you have any indication of when this bug will be closed? It's currently
holding up the (proper) fixes for several bugs key to the Python 2.6
transition, that we want to get over and done as soon as possible.
We can make ugly patches, but fix
support it. python3.2 3.2~a2 is not
proposed for squeeze and only available in experimental to demonstrate
the coexistence of different python3 versions.
Scott Kitterman
Piotr Ożarowski
Barry Warsaw
Matthias Klose
[1] http://python.org/dev/peps/pep-3147/
[2] http://python.org/dev/peps
cim-python
IV
salome (U)
Matthias Jahn
libopensync-plugin-python
Michael Janssen
player
Matthias Klose
zope.testing (U)
martin f krafft
libbuffy-bindings (U)
Noèl Köthe
samba4 (U)
Steve Langasek
samba4 (U)
Georg W. Leonhardt
kaa-imlib2 (U)
Francesco Paolo
On 23.10.2010 13:26, Julian Andres Klode wrote:
On Fr, 2010-10-22 at 14:18 -0400, Barry Warsaw wrote:
On Oct 22, 2010, at 07:52 PM, Julian Andres Klode wrote:
Tell that the Arch people:
http://www.archlinux.org/news/python-is-now-python-3/
Yep, they switched /usr/bin/python to Python 3.X
On 11/28/2011 09:25 PM, Stefano Rivera wrote:
> Of course, it would have to be packaged as a separate Python stack,
> again. Although it would be interesting to allow modules to be built for
> alternate Python implementations, but that's not a trivial project...
maybe for binary packages, but ther
On 11/29/2011 09:56 AM, Maciej Fijalkowski wrote:
> For what is worth, the .py files (but not the .pyc files) can be
> shared among pypy and cpython.
IMO, patching pypy to lookup e.g. .pycp files before .pyc files would be
appropriate for Debian (already doing something like this for .so files in
On 01/04/2012 01:58 PM, Luca Falavigna wrote:
> Hi,
>
> I was pointed at ordereddict package in the NEW queue, which is a
> backport of OrderedDict object, also available in stock python2.7.
please reject it for now.
> After switching python-defaults to python2.7, I'm not sure we
> discussed whe
On 16.03.2012 02:15, Thomas Kluyver wrote:
After some trial and error, I've got it building python3-numpy
(leaving python-support in place for Python 2) - a patch is attached.
I've checked that I can install and import the built package.
Changes and suggestions are welcome, and I expect there ar
On 16.03.2012 14:29, Jakub Wilk wrote:
* Matthias Klose , 2012-03-16, 13:36:
re-adding myself as an uploader, apparently silently removed.
Well, from my IRC log (2011-08-27):
22:43 < jwilk> morph_: Out of interest, did you ask the former Numpy
co-maintainers if they are ok with removin
thon-uniconvertor (U)
Maintainers of GStreamer packages
moovida-plugins-bad
pigment-python
Mark Purcell
hplip (U)
martin f. krafft
python-docutils (U)
Martin Pitt
calibre (U)
Mathieu Malaterre
pylibtiff (U)
Matthew Johnson
fretsonfire (U)
Matthias Klose
python
Am 11.02.2013 17:16, schrieb Barry Warsaw:
> On Feb 11, 2013, at 05:05 PM, Piotr Ożarowski wrote:
>
>> how about replacing python-imaging with python-pil in all packages that
>> do not need compat code (anymore) - this way all packages that are still
>> "broken" will have python-imaging as a depen
Am 14.02.2013 21:54, schrieb Thomas Kluyver:
> On 14 February 2013 20:29, Barry Warsaw wrote:
>
>> I look at the switch to dh_python2 as an example.
>
>
> 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
Am 20.02.2013 00:53, schrieb Piotr Ożarowski:
> [Barry Warsaw, 2013-02-19]
>> So I still think it comes down to, them that does the work gets to
>> decide, but there *is* work to do. It's clear we don't want multiple
>> vcses. So I think you have an opportunity to convince us by:
>>
>> * Doing a
Am 20.02.2013 09:31, schrieb Thomas Goirand:
> On 02/20/2013 12:38 PM, Scott Kitterman wrote:
>> 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
Am 20.02.2013 15:38, schrieb Olе Streicher:
> Hi,
>
> I am trying to create packages for Python3 for the source package
> [1]. Following the guide [2], I get some success. However, the packages
> for Python2 and Python3 differ significantly: in the Python2 package,
> all machine independent data g
Am 06.05.2013 19:45, schrieb Tshepang Lekhonkhobe:
> On Mon, May 6, 2013 at 5:34 PM, Barry Warsaw wrote:
>> * Python 3.4 beta 1 is currently scheduled for November 23, 2013. What
>> should
>> our plans be related to 3.4? My current thinking is that we could support
>> 3.4 but not make it th
Am 13.05.2013 19:21, schrieb Steve Langasek:
> On Sat, May 11, 2013 at 12:29:07AM +0200, Piotr Ożarowski wrote:
>> [Jakub Wilk, 2013-05-10]
>>> postinst
>> [...]
>>> Proposed solution: 1) Wait until #671711 is fixed. 3) Make pycompile a
>>> shell script that does only two simple things: -
Am 11.06.2013 08:18, schrieb Arnaud Fontaine:
> Hello,
>
> No reply so I guess it should be ok. Therefore, I will request the
> removal of python from experimental.
please wait until the upload in NEW reaches unstable, and then it will be
removed automatically.
--
To UNSUBSCRIBE, email
On 06/29/13 16:53, Thomas Kluyver wrote:
> On 22 May 2013 16:28, Barry Warsaw wrote:
>
>> I think we should consider switching back to setuptools once 0.7 is
>> released
>> (defined as "available on PyPI), since this will clearly be the future of
>> this
>> component. We may have some fallout to
Am 10.07.2013 16:30, schrieb Stuart Prescott:
> 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 there t
Am 18.09.2013 09:48, schrieb Julien Cristau:
> On Wed, Sep 18, 2013 at 09:38:57 +0200, Paul Wise wrote:
>
>> We don't do "private copies" or "bundled copies" in Debian, so I guess
>> the right way to go for Debian is to have python depend on python-pip
>> and python3 depend on python3-pip?
>>
> We
Am 19.09.2013 00:36, schrieb Scott Kitterman:
>
>
> 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'r
Am 22.01.2014 08:28, schrieb Thomas Goirand:
> On 01/22/2014 12:24 PM, Barry Warsaw wrote:
>> Do you really think that it's unfeasible for git proponents on this team to
>> find the necessary resources to plan an orderly en mass transition? It might
>> indeed be so, we're all busy. But let's hope
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 m
Am 27.01.2014 00:14, schrieb Nicolas Dandrimont:
> - Adding Python 3 support when upstream has it
I think this should make it into the python policy.
Matthias
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists
Am 26.01.2014 19:59, schrieb Matthias Klose:
> 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
Am 21.03.2014 13:23, schrieb Piotr Ożarowski:
[Barry Warsaw, 2014-03-19]
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. :)
IMO our ensurepip.py should look simil
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/tags/dh_pysupport-is-obsolete.html
>
> Do you think it would be the right time to prepare a mass bug filing
> asking to c
Am 07.05.2014 10:16, schrieb Piotr Ożarowski:
> [Barry Warsaw, 2014-05-07]
>> Generating the wheels during package build is pretty easy I think. You just
>> B-D on python*-wheel (which just got approved from NEW) and then if the
>> package uses setuptools, you just add something like:
>>
>> py
Am 07.05.2014 12:17, schrieb Piotr Ożarowski:
> dh_python2 ignores python3-* packages, dh_python3 ignores python-*
> packages, but in all other packages both of them will try to handle .py
> files. To avoid possible unnecessary dependencies or shebang rewrites,
> debhelper's -N (--no-package) or -p
Attached is a proposed change to the Debian Python policy to focus on Python3
within the distribution. The intent is to document and start a large journey
towards one Python stack in Debian. This is unlikely to happen for jessie+1, but
we should state the plan now so that it doesn't come later as
Am 07.05.2014 17:27, schrieb Barry Warsaw:
>> +
>> +
>> +
>> + Applications should use Python3, and should not be
>> + packaged for Python2 as well.
>> +
>
> Maybe also that system scripts written in Python should be Python 3 and not
> Python 2. I'd add
Am 07.05.2014 23:01, schrieb Steve Langasek:
> On Wed, May 07, 2014 at 10:15:37PM +0200, Matthias Klose wrote:
>> Am 07.05.2014 17:27, schrieb Barry Warsaw:
>>>> + ++ + Applications
>>>> should use
>>>> Python3, and should
Am 07.05.2014 16:45, schrieb Matthias Klose:
> Attached is a proposed change to the Debian Python policy to focus on Python3
> within the distribution. The intent is to document and start a large journey
> towards one Python stack in Debian. This is unlikely to happen for jessie+1,
&
While there are many issues, and not all of these are even fixed upstream, I
think it makes sense to track issues about Python 2 usage, and where it can be
converted / replaced by Python 3. Even if an upstream doesn't plan to support
Python 3 in the future, it makes sense to tag such an issue 'ups
dh_python2 in unstable, dh-python (1.20140511-1) and python-defaults (2.7.6-1)
now don't create symlinks to /usr/{lib,share}/pyshared anymore, but install
directly to /usr/lib/python2.7/dist-packages. There are a lot of packages
affected, so maybe the complete removal cannot be done in time for th
Issue #748299 asks about adding wheel support for setuptools. I know about the
special case for pip and it's dependencies, however I would like to see to have
wheel support addressed first before applying such a patch.
- should we add wheels everywhere? I don't think we should,
but I'd like t
Am 16.05.2014 10:48, schrieb Piotr Ożarowski:
> If I provide a script that generates .whl file out of Debian binary
> package, would that make more sense than these -wheels packages?
>
> python3.X-venv could simply depend on required packages and run this
> script (with a list of required dependen
Am 16.05.2014 00:32, schrieb Barry Warsaw:
> 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.
>
Am 19.05.2014 12:19, schrieb Piotr Ożarowski:
> please at least unpack these wls files so that admins don't have to
> figure out what to do with them if they want to apply a patch from
> upstream
no, you don't gain anything by this. we don't unpack jar files either.
Matthias
--
To UNSUBSCRI
Am 19.05.2014 13:19, schrieb Jakub Wilk:
> * Matthias Klose , 2014-05-19, 12:44:
>> we don't unpack jar files either.
>
> Fortunately, we don't have to mimic all the Java misfeatures.
fine, then please come back after changing the policy to ship unpacked .a files.
Call
Am 14.07.2014 08:25, schrieb Jan Dittberner:
> On Mon, Jul 14, 2014 at 02:09:36PM +1000, Brian May wrote: python-pika
> depends on Twisted which is Python 2 only, upstream supports Python 2 only
> too. The Pika documentation has a statement "Currently pika only supports
> Python 2.6 and 2.7. Work t
Am 23.07.2014 03:38, schrieb Olly Betts:
> Package: release.debian.org Severity: normal User:
> release.debian@packages.debian.org Usertags: transition Control: block
> -1 by 734799
>
> This is a follow-on from the wxwidgets3.0 transition. The wxwidgets2.8
> source package actually contains
Am 23.07.2014 15:07, schrieb Olly Betts:
> On Wed, Jul 23, 2014 at 02:10:19PM +0200, Matthias Klose wrote:
>> Am 23.07.2014 03:38, schrieb Olly Betts:
>>> The intention is to eliminate wxwidgets2.8 (and hence wxpython 2.8) before
>>> releasing jessie - the last upstream
Am 28.07.2014 um 14:00 schrieb Debian FTP Masters:
>
>
> Accepted:
>
> Format: 1.8
> Date: Mon, 30 Jun 2014 10:04:06 +0200
> Source: python-pandocfilters
> Binary: python-pandocfilters python3-pandocfilters
> Architecture: source all
> Version: 1.2.1-1
> Distribution: unstable
> Urgency: low
> M
Am 07.08.2014 um 23:48 schrieb Raphael Hertzog:
> Hi,
>
> I rebuilt all reverse deps of python-django and I tagged confirmed all the
> associated bugs where the package failed to build with python-django 1.7
> and I sent the relevant extract of the build log...
a lot of django packages are still
Seen this in pycurl (#757694), but if this is something which occurs more often,
then I think we should prepare for a policy update and/or a lintian warning.
Maybe it is not yet possible to avoid one stack entirely, but we should not
create artificial dependencies.
Matthias
--
To UNSUBSCRIBE
Control: severity -1 important
> That's a bug in the test (race condition) rather than in the program.
> It's fixed upstream.
Nikolaus, I find this kind of attitude rather disturbing. If you don't care
about the autopkg tests, and if you are not ready to fix these but rather wait
for the fixes f
Am 20.08.2014 um 06:52 schrieb Nikolaus Rath:
> If someone cares deeply about this, the necessary patch is at
> https://bitbucket.org/nikratio/s3ql/commits/9a8c0ebbff390555e63b7e203b999b89aabbb86e/raw/.
>
>
> I did not add it to the debian package yet because I considered it a
> minor issue tha
Am 11.09.2014 um 10:30 schrieb Piotr Ożarowski:
> [Andreas Tille, 2014-09-11]
>> pkg_resources.DistributionNotFound: pil>=1.1.7
>
> python{,3}-pil provides Pillow egg-info
> Matthias: should python-imaging provide pil.egg.info file (for older
> libraries/applications like dicompyler?
I don't mind
Am 17.10.2014 um 17:03 schrieb Barry Warsaw:
> Hi Florent,
>
> On Oct 17, 2014, at 04:17 PM, Florent Rougon wrote:
>
>> As the upstream maintainer of pythondialog, I feel a bit concerned about
>> its status in Debian, in particular about what is going to go into
>> jessie. In short, I'd rather se
On 11/19/2014 12:45 AM, Yannick Roehlly wrote:
Hi,
The building of Python 2 without SSLv3 support breaks requests:
import requests
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python2.7/dist-packages/requests/__init__.py", line 68, in
_attach_namespace(ur
Hi, I won't have the time to do that, CCing debian-python. You may want to ask
for a sponsor there, or even join the python-modules team.
Matthias
On 02/06/2015 06:23 AM, Riley Baird wrote:
> Hi Matthias,
>
> A couple of years ago, you orphaned the "slides" package. I'd like to
> adopt it, but s
On 02/11/2015 04:04 PM, Michael Crusoe 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 version with a
> mutliarch triplet:
On 03/23/2015 02:38 PM, Barry Warsaw wrote:
> On Mar 23, 2015, at 11:25 AM, Piotr Ożarowski wrote:
>
>> I can change that and remove them in first dh-python's Stretch upload if
>> there's an agreement to do that.
>
> +1. pth files are evil. If stuff breaks because of their removal, we'll have
>
On 04/13/2015 11:07 PM, Donald Stufft wrote:
>
>> On Apr 13, 2015, at 4: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?
>>
>> Matthias wants to dis
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 the number
of '2' and '3' digits in the date, when you're tryin
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 team, so, does anyone object to
> me asking people to not write n
On 05/11/2015 04:08 AM, Ben Finney wrote:
> "Paul R. Tagliamonte" writes:
>
>> That or symlink them in from /usr/share ;)
>
> Yes, that works too (and I've done it in my packages):
>
> Use ‘dh_install’ to install the non-program files to the correct
> location under ‘/usr/share/foopackage/’, an
On 05/11/2015 09:03 AM, Ole Streicher wrote:
> Ben Finney writes:
>> Ole Streicher writes:
>> Installing the non-program files to ‘/usr/share/foopackage/images/’ (for
>> example) is simple enough, using ‘dh_install’.
>
> I am using pybuild, and I am wondering why it doesn't do this
> automatical
On 05/11/2015 04:27 AM, Ben Finney wrote:
> Matthias Klose writes:
>
>> there are some discussions on the distutils SIG where to move certain
>> types of files.
>
> Can you please show a URL to a specific discussion you think would
> benefit from a Debian contributio
The packages built for the Python debug interpreters should not be stripped.
Usually this has to be done on a per package basis, however when converting to
the pybuild system, this is easily missed. It is now documented in [1], but I
assume a lot of packages just strip the -dbg packages. Maybe lint
On 06/30/2015 12:04 AM, Barry Warsaw wrote:
>> At the same time - are there plans to upload python3-defaults with enabled
>> support for Python 3.5?
>
> Yes, but atm, there's no eta.
wrong. it's in experimental.
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject
On 07/09/2015 12:25 PM, Robert Collins wrote:
> On 3 July 2015 at 08:29, Scott Kitterman wrote:
>
>> I think dropping these duplicates is the only thing that makes sense. For
>> reference, I dropped python3-ipaddr once python3.2 was gone (because 3.3 has
>> ipaddress, which does the same thing).
On 09/06/2015 04:24 PM, Scott Kitterman wrote:
> On Sunday, September 06, 2015 08:23:37 AM PICCA Frederic-Emmanuel wrote:
>> Hello, guyes,
>>
>> I am working on this bug report[1], and I would like your opinion.
>> this package depends on the tango library which was rebuilt with gcc5 and
>> updated
kindergarten ...
On 30.09.2015 21:41, Thomas Goirand wrote:
Hi,
Piotr decided to remove me from the Python team. Those who don't agree
(especially admins) please voice your concern. It is my view that this
is an over reaction and that it should be reverted.
Thomas Goirand (zigo)
On 07.10.2015 11:46, Piotr Ożarowski wrote:
[Jan-Pascal van Best, 2015-10-07]
I look forwarded to working with you on Python packaging. If I'm
accepted into the team, I'll upload the packaging work up to now to
oh, best join request so far!
do you call him by name or value? ;)
On 26.10.2015 12:36, Piotr Ożarowski wrote:
there are manpages: pybuild¹, dh_python3² / dh_python2³ / dh_pypy⁴
there's a wiki page⁵ with examples, there's even
/usr/share/doc/dh-python/README.PyDist⁶ and a talk⁷ about pybuild during
DebConf... but people still tell me dh-python's documentation su
1 - 100 of 512 matches
Mail list logo
