.Y --libs", so
> -lpythonX.Y is added.
Your package is wrong. The python-config script is for linking the
interpreter into a binary, not for building extensions.
Extensions must not link to libpython by themselves.
Cheers,
--
.''`. Josselin Mouette
: :' :
`. `'
t; The first variant seems to be more common
I guess you mean the opposite. In any case that would be a bug to ship
debugging modules in a regular package.
Cheers,
--
.''`. Josselin Mouette
: :' :
`. `'
`-
signature.asc
Description: This is a digitally signed message part
hat among the things I’d like to write, but it
would be very long so I haven’t found the time yet.
--
.''`. Josselin Mouette
: :' :
`. `'
`-
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of "unsubscribe". Trou
scripting and small applications).
--
.''`. Josselin Mouette
: :' :
`. `'
`-
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/1308038941.18675.292.camel@pi0307572
ake our
> packages more sensible, while we continue to advocate for upstream
> behaving the way we want.
I still fail to see why we couldn’t patch Python in Debian to behave in
a correct way, especially wrt. the bytecompiled modules location. We
don’t have to wait for upstream to do that.
--
ckages. ${python:Provides} is incorrect for any
package that has other Python packages as dependencies.
Thanks,
--
.''`. Josselin Mouette
: :' :
`. `' “If you behave this way because you are blackmailed by someone,
`-[…] I will see what I can do for you.” -- Jörg Schilling
Le jeudi 10 mars 2011 à 09:00 -0500, Scott Kitterman a écrit :
> The upstream Python position is (I'll paraphrase), "There will not be
> a Python 2.8. If there is a new feature release of Python 2 it will be
> because someone forked it - it's Free software, so we can't prevent
> that".
>
> There a
Le lundi 03 janvier 2011 à 12:26 +0100, Michael Fladischer a écrit :
> I've filed bugs with severity minor to all (30) affected packages
> (except python-sphinx, thanks for the quick fix :-) ).
You might want to close them or merge them with #608907 which contains
the correct fix.
Cheers,
--
.
Le lundi 03 janvier 2011 à 00:17 +0100, Michael Fladischer a écrit :
> Some packages (e.g. python-sphinx itself) ship a gzip compressed
> objects.inv.gz (it seems to me that dh_compress triggers this during
> build) but sphinx.ext.intersphinx is not able to read compressed files.
If it’s done by d
Le lundi 18 octobre 2010 à 15:21 +0200, Tshepang Lekhonkhobe a écrit :
> That's overly pessimistic. I'm on the other end of extreme: Wheezy CAN
> release with Py3k as default version. There's a lot of porting efforts
> going on, and Debian would be heroic to be one of the long term
> releases (earl
Le lundi 27 septembre 2010 à 20:02 +0100, Adam D. Barratt a écrit :
> On Mon, 2010-09-27 at 09:51 +0200, Josselin Mouette wrote:
> > Le dimanche 26 septembre 2010 à 23:53 +0200, Jakub Wilk a écrit :
> > > >gnome-python-extras 2.25.3-5
> > > python-gda depends on b
Le dimanche 26 septembre 2010 à 23:53 +0200, Jakub Wilk a écrit :
> >gnome-python-extras 2.25.3-5
> python-gda depends on both python2.5 and libpython2.6.
Fixed in 2.25.3-6. Please unblock.
Cheers,
--
.''`. Josselin Mouette
: :' :
`. `' “If you be
Le dimanche 22 août 2010 à 14:38 +0200, Piotr Ożarowski a écrit :
> > Apt-file suggests that runpy is only available in python2.7, that is not
> > installed in my system. But actually, python-markupsafe is not
> > the only module needing runpy: at least python-imaging-tk and
> > python-pkg-resourc
Le mardi 27 juillet 2010 à 10:33 +0900, Shyouzou Sugitani a écrit :
> After upgrading from 2.17.0-2 to 2.17.0-3 I got an error
> "pygtk was not compiled with Numeric Python support".
>
> $ python
> >>> import gtk
> >>> pixbuf = gtk.gdk.Pixbuf(gtk.gdk.COLORSPACE_RGB, True, 8, 100, 100)
> >>> pixbuf
Le lundi 19 juillet 2010 à 21:27 +0100, Antoine Sirinelli a écrit :
> Hello everybody,
>
> It seems that since the last numpy upload, pytables is no longer working. I
> have filled a bug report
> (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=589669) but my question is
> more general. It seems
Le lundi 19 juillet 2010 à 19:04 +1000, Brian May a écrit :
> Django applications come with a number of options to deploy under a
> webserver. My preferred in fastcgi, but this obviously isn't going to
> suit Debian, due to the non-freeness of fastcgi.
Only for apache. FastCGI support is built-in
For example, support for
autotools Python packages has been recently added - and this is
something that dh can’t do.
I think there are more urgent matters to settle than picking over a
developer’s build system choice.
--
.''`. Josselin Mouette
: :' :
`. `' “If you
Le mercredi 23 juin 2010 à 21:17 -0400, Scott Kitterman a écrit :
> >5. End this madness and use the version in build-dependencies instead of
> >asking maintainers to specify it twice - which they usually do wrong.
> >
> With this approach then with the current python-defaults in Sid, how would
>
for Python3 versions
5. End this madness and use the version in build-dependencies instead of
asking maintainers to specify it twice - which they usually do wrong.
--
.''`. Josselin Mouette
: :' :
`. `' “If you behave this way because you are blackmailed by someone,
`-
Le lundi 26 avril 2010 à 11:04 +0100, Floris Bruynooghe a écrit :
> On Mon, Apr 26, 2010 at 09:44:52AM +0200, Josselin Mouette wrote:
> > Unfortunately that won’t work, since the rpath used by dlopen() is the
> > one provided by the binary, not the one for the module being loade
ch cases. But it will prevent
the Python module from loading given how the toolchain currently works.
Cheers,
--
.''`. Josselin Mouette
: :' :
`. `' “A handshake with whitnesses is the same
`- as a signed contact.” -- Jörg Schilling
--
To UNSUBSCRIBE, email to de
for its NEEDED components and load them manually using
the given rpath before loading the actual module.
Which in turn will not be possible since there is no shared version of
libbfd - which would be required for doing this.
Cheers,
--
.''`. Josselin Mouette
: :' :
`. `' “
versions by a given module. So even
without a symlink farm, there is at least some magic needed to indicate
which versions are supported, maybe in the .py files themselves.
Cheers,
--
.''`. Josselin Mouette
: :' :
`. `' “If you behave this way because you are blackmailed by
__init__.py file instead?
(I have no idea what declare_namespace does.)
If so, you can rely on python-support creating that file automatically.
Otherwise, I guess the only approach is indeed to make a Debian-specific
package to ship that file.
Cheers,
--
.''`. Josselin Mouette
t; > pyshared/$PACKAGE_NAME/ ??
>
> Why do you want to install to pyshared/$PACKAGE_NAME/?
Maybe so that the package doesn’t take 6 new names in the root
namespace?
--
.''`. Josselin Mouette
: :' :
`. `' “I recommend you to learn English in hope that you
ython2.6
> | ln -sf python2.6 /usr/bin/python
> | sed -i 's/^default-version =.*/default-version = python2.6/g' \
> | /usr/share/python/debian_defaults
> | }
> `
This doesn’t take into account the fact that for dependencies, the
python package itself should have a
before and make it painless for users.
--
.''`. Josselin Mouette
: :' :
`. `' “I recommend you to learn English in hope that you in
`- future understand things” -- Jörg Schilling
signature.asc
Description: Ceci est une partie de message numériquement signée
libraries and applications, they're YAGNI anyway. If there
> are specific problems with Python tools for the majority of straightforward
> Python libraries, let's fix those tools. But I think they mostly work, and
> where they don't, the distutils-sig is paving the way of
he insanity of libtool
bugs, the arcanes of m4 and the gazillions of broken m4 scripts that lie
around… But these flaws are about features that don’t even exist in
Python-specific tools.
Cheers,
--
.''`. Josselin Mouette
: :' :
`. `' “I recommend you to learn English in h
ptools are not able to
do that, not unless you bundle specific scripts with your packages.
--
.''`. Josselin Mouette
: :' :
`. `' “I recommend you to learn English in hope that you in
`- future understand things” -- Jörg Schilling
signature.asc
Description: Ce
somewhere in the
design process.
__file__ is a plague. If it wasn’t here, people would have, long ago,
developed correct distribution systems for Python instead of using such
an unreliable way of determining the filesystem layout.
--
.''`. Josselin Mouette
: :' :
`. `'
lling files to the right place depending on the
configuration; after all it was designed for that.
--
.''`. Josselin Mouette
: :' :
`. `' “I recommend you to learn English in hope that you in
`- future understand things” -- Jörg Schilling
signature.asc
Description: Ceci est une partie de message numériquement signée
Le mardi 19 janvier 2010 à 20:45 +0100, Piotr Ożarowski a écrit :
> [Josselin Mouette, 2010-01-19]
> > Le vendredi 15 janvier 2010 à 11:58 +0100, Piotr Ożarowski a écrit :
> > > - starting/stopping daemons problems (very long downtimes due to byte
> > > compilation
ery
small set of Python packages, namely those on which the package managers
depend. For the rest of the archive, I just don’t see the point.
Introducing this way of doing things in a subset of Python packages
sounds interesting - either for a small set, or for all
architecture-dependent packages. Doing
evertheless.
--
.''`. Josselin Mouette
: :' :
`. `' “You did never write something helpful
`- besides your trolling” -- Jörg Schilling
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
ow what these mean, you should not make Debian
packages of any kind. Really.
--
.''`. Josselin Mouette
: :' :
`. `' “I recommend you to learn English in hope that you in
`- future understand things” -- Jörg Schilling
--
To UNSUBSCRIBE, email to debian-pyt
ny".
You have to be kidding.
Especially, a more Python-oriented description (talking about the
difference between pure-Python modules and C extensions) is already
included in this file.
--
.''`. Josselin Mouette
: :' :
`. `' “I recommend you to learn English in h
gt; >advice. Thank you.
> >
> My advice would be wait.
OTOH porting from python2.6 to python2.5 should be really easy, there
have been very few language additions to python2.6. This would allow
your software to also work on Debian stable, as well as some other major
releases of other dis
e python (>= X.Y), python (<< X.Y+1) in this case, but it is
precisely the kind of ideas that make transitions a nightmare.
Cheers,
--
.''`. Josselin Mouette
: :' :
`. `' “I recommend you to learn English in hope that you in
`- future understand things” -
trictly similar to making mandatory the documentation of dependencies.
Cheers,
--
.''`. Josselin Mouette
: :' :
`. `' “I recommend you to learn English in hope that you in
`- future understand things” -- Jörg Schilling
signature.asc
Description: Ceci est une partie de message numériquement signée
as the reference version is in the
python-defaults package.
Cheers,
--
.''`. Josselin Mouette
: :' :
`. `' “I recommend you to learn English in hope that you in
`- future understand things” -- Jörg Schilling
signature.asc
Description: Ceci est une partie de message numériquement signée
at /usr/share/$package
and /usr/lib/$package.
Cheers,
--
.''`. Josselin Mouette
: :' :
`. `' “I recommend you to learn English in hope that you in
`- future understand things” -- Jörg Schilling
signature.asc
Description: Ceci est une partie de message numériquement signée
n2.4 setup.py install"?
>
> No, the problem is, loosely speaking, that python is on crack.
Actually you are both right; setuptools is on crack for modifying the
shebang, and IIRC distutils does the same.
--
.''`. Josselin Mouette
: :' :
`. `' “I reco
Le vendredi 18 septembre 2009 à 21:18 +0200, Josselin Mouette a écrit :
> If there are no objections, I will submit a MBF for those 75 packages in
> a few days.
Done, omitting a reported false positive and a few packages fixed in the
meantime.
http://bugs.debian.org/cgi-bin/pkgreport.cgi
ir number, this should probably be a lintian warning instead.
Cheers,
--
.''`. Josselin Mouette
: :' :
`. `' “I recommend you to learn English in hope that you in
`- future understand things” -- Jörg Schilling
signature.asc
Description: Ceci est une partie de message numériquement signée
Le vendredi 18 septembre 2009 à 21:18 +0200, Josselin Mouette a écrit :
> * 246 packages don’t, but should work as well provided that we
> ensure python-central is fixed.
I forgot to explain how exactly it needs to be fixed.
> * python-central needs a NMU to
> han
).
* python-central needs a NMU to
handle /usr/lib/python2.6/site-packages as a source directory.
* 75 Python packages need to be updated, the dd-list is attached.
If there are no objections, I will submit a MBF for those 75 packages in
a few days.
Cheers,
--
.''`.
e them
all to work with python2.6.
Cheers,
--
.''`. Josselin Mouette
: :' :
`. `' “I recommend you to learn English in hope that you in
`- future understand things” -- Jörg Schilling
signature.asc
Description: Ceci est une partie de message numériquement signée
tch, so I guess you can go
ahead if you want.
--
.''`. Josselin Mouette
: :' :
`. `' “I recommend you to learn English in hope that you in
`- future understand things” -- Jörg Schilling
signature.asc
Description: Ceci est une partie de message numériquement signée
s will
> use the new approach?
I think that’s the most efficient approach indeed. For that, we need to
either:
* patch /usr/bin/pyversions to use them instead
* or introduce a new script that does this, and get cdbs and dh7
to use it instead
--
.''`. Josse
ing them
twice.
> What about XB-Python-Version, is this field still useful?
The only thing that used it was python-central, and it now stores the
information on-disk, in /usr/share/pyshared-data/$package. So I think it
could be removed.
Cheers,
--
.''`. Josselin Mouette
: :' :
the list of python versions to build for.
Cheers,
--
.''`. Josselin Mouette
: :' :
`. `' “I recommend you to learn English in hope that you in
`- future understand things” -- Jörg Schilling
signature.asc
Description: Ceci est une partie de message numériquement signée
#x27;t do what was asked for.
Please stop distorting facts.
--
.''`. Josselin Mouette
: :' :
`. `' “I recommend you to learn English in hope that you in
`- future understand things” -- Jörg Schilling
signature.asc
Description: Ceci est une partie de message numériquement signée
have never been
more than an implementation detail for python-central.
Cheers,
--
.''`. Josselin Mouette
: :' :
`. `' “I recommend you to learn English in hope that you in
`- future understand things” -- Jörg Schilling
signature.asc
Description: Ceci est une partie de message numériquement signée
Le mardi 01 septembre 2009 à 13:53 +0300, anatoly techtonik a écrit :
> Can anybody point me to the repository location of python-support package?
It’s in collab-maint :
http://svn.debian.org/viewsvn/collab-maint/deb-maint/python-support/trunk/
Cheers,
--
.''`. Jos
orking
> on it?
In the current state of affairs and given the plans of the Python
maintainers, there will be likely no python2.6 (even as non-default) in
squeeze.
Cheers,
--
.''`. Josselin Mouette
: :' :
`. `' “I recommend you to learn English in hope that you in
`-
for all supported versions.
AFAIK pyversions -r gives the same output as pyversions -s if no version
information is found.
--
.''`. Josselin Mouette
: :' :
`. `' “I recommend you to learn English in hope that you in
`- future understand things” -- Jörg Schilling
si
onus, you can communicate with assholes from
Auckland, isn’t that great?
Thanks a lot, Sam.
--
.''`. Josselin Mouette
: :' :
`. `' “I recommend you to learn English in hope that you in
`- future understand things” -- Jörg Schilling
signature.asc
Description: C
Le mercredi 29 avril 2009 à 22:50 +1200, itsovermyhead a écrit :
> The colon ( : ) has multiple uses.
And that’s not something that could be said about you.
--
.''`. Josselin Mouette
: :' :
`. `' “I recommend you to learn English in hope that you in
`- f
, why did you break the installation
so badly to begin with?
--
.''`. Josselin Mouette
: :' :
`. `' “I recommend you to learn English in hope that you in
`- future understand things” -- Jörg Schilling
signature.asc
Description: Ceci est une partie de message numériquement signée
Le lundi 20 avril 2009 à 15:55 +0200, Piotr Ożarowski a écrit :
> [LI Daobing, 2009-04-20]
> > The update-python-modules script is provided by:
> > ii python-support 0.8.7 automated rebuilding
> > support for Python modules
>
> let me guess: your package should depend on pytho
Le mercredi 15 avril 2009 à 15:17 +0200, Piotr Ożarowski a écrit :
> how about:
> * moving all files to usr/share/pyshared (just like you do now)
> * registering files basing on usr/share/pyshared content (ignore
> old .public/.private files)
I’m afraid this would lose some information on the su
Le mercredi 15 avril 2009 à 14:19 +0200, Piotr Ożarowski a écrit :
> oh, you can't - dh_pysupport doesn't pick up files from /usr/share/pyshared
> (Joss: could you add this path to movemodules?)
It’s not that simple, since that would prevent dh_pysupport from being
idempotent. I guess I could just
Le mercredi 15 avril 2009 à 08:01 +1000, Ben Finney a écrit :
> > If there is no upstream build system, you need to replace it, and
> > the .install file looks like the simplest way to do it. I don’t
> > understand why you’d want to drop it.
>
> Because it's double-handling: in the ‘debian/rules’
Le mardi 14 avril 2009 à 22:09 +1000, Ben Finney a écrit :
> What about in this case, where there *is* no upstream build system for
> these modules and the only supported install method is “copy the module
> files where you want them”?
>
> Where should I put the upstream library files so that the
Le mardi 14 avril 2009 à 16:51 +1000, Ben Finney a écrit :
> > Put them into /usr/lib/python*/site-packages, as documented in its
> > manpage?
>
> Thanks. That's new since the version of ‘python-support’ currently in
> ‘squeeze’. (The ‘dh_pysupport(1)’ manpage in version 0.8.7 still talks
> about
I have just uploaded version 0.95.0 renamed as 1.0.0:
python-support (1.0.0) unstable; urgency=low
* Upload to unstable.
This accounts for 24 remaining bugs that are now RC, you can now start
hating me.
--
.''`. Debian 5.0 "Lenny" has been released!
: :' :
`. `' Last night, Darth Vad
Le lundi 30 mars 2009 à 14:50 +0200, Karsten Hilbert a écrit :
> On Mon, Mar 30, 2009 at 02:18:31PM +0200, Josselin Mouette wrote:
>
> > > - modify sys.path inside gnumed.py appropriately
> > > (which I disapprove of as it means moving
> > >platform spe
Le lundi 30 mars 2009 à 12:26 +0200, Karsten Hilbert a écrit :
> - use Gnumed.pth in site-packages/
> (which higher wizards around here discourage us to do)
Please don’t! This completely defeats the point of shipping packages in
a private directory.
> - link /usr/share/gnumed/Gnumed into si
Le lundi 30 mars 2009 à 12:18 +0200, Karsten Hilbert a écrit :
> For what it's worth the gnumed.py outermost Python script sayeth:
>
> #!/usr/bin/env python
>
> and, then, even that is ignored because the /usr/bin/gnumed
> shell script calls gnumed.py via "python -m".
Which means using the defau
Le dimanche 29 mars 2009 à 20:46 +0200, Karsten Hilbert a écrit :
> I believe Andreas was wondering about the pre-compiled pyc files being
> installed alongside the py files. If they are stored there they can
> only be precompiled by one particular Python version at a time. This made
> us wonder wh
Le vendredi 27 mars 2009 à 18:30 -0300, Gustavo Franco a écrit :
> Hi Joss,
>
> Is it done?
Not yet, I forgot a few words in my original mail :)
> > Until there are important objections against it, I will do this move,
in a week or so
> > and bump the priorities of the remaining bugs to se
Hi again,
with finally proper support for the dist-packages and /usr/local changes
in python2.6, I think python-support should be ready to move from
experimental to unstable.
Unfortunately, there are still a number of packages that will break when
this happens:
http://bugs.debian.org/cgi
Le mercredi 25 mars 2009 à 22:53 +0100, Piotr Ożarowski a écrit :
> I hope we'll find a way to make sure python-central will be the first
> one which will be upgraded (Pre-Depends somewhere? Backporting some
> changes in Lenny's python-central?)
Making one package (e.g. python-support) conflict wi
Le mercredi 25 mars 2009 à 22:22 +0100, Piotr Ożarowski a écrit :
> * python2.6 is using dist-packages instead of site-packages and it installs to
> /usr/local by default:
>
> + add "--install-layout=deb" option to setup.py call in debian/rules (or
> py_setup_install_args from python.mk, s
Le lundi 16 mars 2009 à 14:08 +0100, Josselin Mouette a écrit :
> 3. GNOME-PYTHON-EXTRAS
>
> What is happening in unstable:
> * egg.trayicon, gtkhtml2 and gtkmozembed each have their own
> binary package (python-eggtrayicon, python-gtkhtml2,
>
)
scribes
update-manager (U)
Sam Morris
serpentine
Josselin Mouette
epiphany-extensions
gedit-plugins (U)
gnome-games
hamster-applet (U)
hotwire
update-manager (U)
Philippe Normand
elisa-plugins-good (U)
Piotr Ożarowski
griffith
Thibaut Paumard
update
Le samedi 07 mars 2009 à 22:17 -0600, Steve M. Robbins a écrit :
> OK. I'm certainly in favour of avoiding complexity. However, I
> thought I was following the python policy [1] where B.1 says:
This document is incorrect. Since it is basically unmaintained and
contains many similar mistakes, you
Le lundi 02 mars 2009 à 16:29 -0800, Steve Langasek a écrit :
> > And well, that might make pretty obvious to anyone not convinced yet
> > that -central can't really be considered a “chosen one”, no?
>
> So how does python-support address this bug without instead making
> python-based programs exc
Le lundi 02 mars 2009 à 15:48 +0100, Vincent Bernat a écrit :
> I ask this because I have many packages that use unittests after the
> build. I add /var/lib/python-support to PYTHONPATH and launch those
> tests. Because the path has changed, this does not work any more.
>
> You suggest to
Le mercredi 18 février 2009 à 23:55 +0100, Josselin Mouette a écrit :
> However I wish I could be so sure about building packages, but the
> metadata format has changed so you can expect some big failures. I have
> used a few sample packages during my testing, but this is far from
>
Le dimanche 22 février 2009 à 12:26 +0100, Vincent Bernat a écrit :
> Do we need to upload a new version when there is a fix needed? In this
> case, I suppose we should use python-support in unstable instead of the
> one in experimental?
Yes, it is possible to fix packages so that they work wit
Le jeudi 19 février 2009 à 18:06 -0500, Guy Hulbert a écrit :
> So *.py ( and *.pyc, iirc ) should be under /usr/share.
>
> Yes:
> http://www.network-theory.co.uk/docs/pytut/CompiledPythonfiles.html
> The contents of the ‘spam.pyc’ file are platform independent, so
> a Python modul
Hi,
I have just uploaded a new version of python-support to experimental. It
includes several major changes:
* Installation directory moved from /var/lib/python-support
to /usr/lib/pymodules
* Public modules moved from /usr/share/python-support/$package
to /usr/share/py
Le mercredi 18 février 2009 à 13:33 +1100, Ben Finney a écrit :
> I saw no response to Message-ID: <87skwceynw@benfinney.id.au> on
> this forum, but would love to be convinced this will be fixed. This is
> probably the last remaining issue keeping me with ‘python-central’ for
> my packages.
As
Le mercredi 18 février 2009 à 02:23 +0100, Piotr Ożarowski a écrit :
> that's exactly what I meant, /usr/lib/py{3,}shared will be equivalent of
> /usr/share/py{,3}shared but for Python extensions, sorry if I sounded
> differently
OK, I misunderstood you then :)
Any comment on the module installat
Le mercredi 18 février 2009 à 01:20 +0100, Piotr Ożarowski a écrit :
> > where is the advantage of having a /usr/lib/pyshared?
>
> it's one of the "sacrifices" you'll have to make if you want
> /usr/share/py{,3}shared to be used by other tool(s). I see no way to use
> Python's official path in pys
Le mardi 17 février 2009 à 10:09 -0800, Ondrej Certik a écrit :
> Unfortunately from both of you I only met Matthias in person (in
> Prague at the Ubuntu Developer Summit), but what I understood is that
> there are some technical reasons why python-central is better.
I’d be happy to hear these re
Le mardi 17 février 2009 à 15:03 +0100, Bernd Zeimetz a écrit :
> > - Can you guys please finally sit down and agree on one solution for
> > handling python modules? I still think that having two (slightly
> > different) ways of doing this task is not the way to go. I really do
> > not see te
Le lundi 16 février 2009 à 22:33 +0100, Matthias Klose a écrit :
> > I really like the idea of using the same location for both tools, please
> > note
> > that you'll have to change pycentral to use something like /usr/lib/pyshared
> > (for Python extensions)
>
> where is the advantage of having
Le mardi 17 février 2009 à 22:06 +1100, Felipe Sateler a écrit :
> Josselin Mouette wrote:
>
> > "XS-Python-Version: current" means the following: even if several Python
> > versions are available, the module will only be built for the default
> > version. *This
Le mardi 17 février 2009 à 10:50 +1100, Felipe Sateler a écrit :
> > "current" does not mean anything, semantically, especially for public
> > modules/extensions. There is a set of supported versions, and that’s
> > all. For extensions, it is the set of versions the extension has been
> > built aga
Le lundi 16 février 2009 à 22:33 +0100, Matthias Klose a écrit :
> "current" is also useful to only provide a public module for just the default
> version. I'm unsure what you mean with when talking about the above mentioned
> "issue"
Is it a joke? If you don’t know what this is about, why are you
Le mercredi 11 février 2009 à 22:48 +0100, Matthias Klose a écrit :
> pygtk requires for some obscure (couldn't
> find code using this) the multiarray extension and depends on it (although an
> exception is thrown at runtime if the extension is not found). while pygtk
> could
> be better packaged,
Le dimanche 08 février 2009 à 21:36 -0800, Ondrej Certik a écrit :
> > should build numpy (and scipy) without ATLAS, even if atlas is detected.
>
> Thanks for the tip --- I think there was some reason for this
> conflict, but I can't remember now. Let's wait a bit what other think
> here.
IIRC th
Le lundi 02 février 2009 à 22:35 -0500, Yaroslav Halchenko a écrit :
> why in a hackish site.py those /usr/local paths are added?
Because we want to follow the FHS, which is all but hackish - but
Python, in many ways, doesn’t make it easy.
The real question is more: why aren’t these paths correc
Le mercredi 24 décembre 2008 à 00:48 +0100, Ondrej Certik a écrit :
> Imho if we are going to only version the debian dir, then I also don't
> see such a strong argument for git (or other distributed vcs). Since
> it will still need to fiddle with upstream tarball and also with
> debian/patches + q
Le lundi 29 septembre 2008 à 15:12 +0200, Nicolas Chauvat a écrit :
> Here is where we stand today:
> http://mail.python.org/pipermail/distutils-sig/2008-September/010126.html
This looks like a step in the right direction if we want to generate
inter-module dependencies.
Most things defined in th
Le vendredi 29 août 2008 à 19:51 +0200, Vincent Bernat a écrit :
> > Could you please test the python-support package at
> > http://malsain.org/~joss/debian/ to see whether it handles this case
> > correctly?
>
> Yes, this works correctly with this version.
OK, uploaded to unstable.
> The init
Le mercredi 27 août 2008 à 23:33 +0200, Marc Fargas a écrit :
> > 3. Due to changes in the admin and form applications, Django 1.0 will be
> > backwards incompatible with 0.96 and the old stable version's use in
> > Debian might be questionable.
>
> That's the second super point, nobody will want
1 - 100 of 353 matches
Mail list logo
