[Josselin Mouette, 2010-01-22]
> 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
> > > >
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 via triggers) in pysupport,
I know I'm coming in the middle of this, and I'm sure I don't understand all
the issues yet, but I'll chime in here anyway. :)
On Jan 19, 2010, at 10:39 AM, Josselin Mouette wrote:
>I’m also still wondering which exact problem this proposal is trying to
>fix. Currently the only thing it does seem
[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 via triggers) in pysupport,
>
> This is only a problem for daemons using namespace packages, which y
Le vendredi 15 janvier 2010 à 11:58 +0100, Piotr Ożarowski a écrit :
> Here's updated dh_python proposal. Main change since my last mail:
> pycompile/pyclean will no longer search for files to compile/remove
> in public directories as Matthias will fix #552595 using triggers so I don't
> have to ca
[Jakub Wilk, 2010-01-15]
> You want to skip only directories without __init__.py and under
> /usr/lib/python*/*-packages/, right? That's fine.
yes (at least by default)
--
Piotr Ożarowski Debian GNU/Linux Developer
www.ozarowski.pl www.griffith.cc www.de
> Here's updated dh_python proposal. Main change since my last mail:
> pycompile/pyclean will no longer search for files to compile/remove
> in public directories as Matthias will fix #552595 using triggers so I
> don't
> have to care about pycentral bugs anymore and dpkg -L seems to be fast
> enou
* Piotr Ożarowski , 2010-01-15, 16:08:
symlinks / private directories if given Python version is installed
(dpkg -L output will be used to detect which files need byte compilation,
directories without __init__.py file will be skipped),
IOW, you want to skip modules that are not a part of a pack
[Jakub Wilk, 2010-01-15]
> * Matthias Klose , 2010-01-15, 14:58:
symlinks / private directories if given Python version is installed
(dpkg -L output will be used to detect which files need byte compilation,
directories without __init__.py file will be skipped),
>>>
>>> IOW, you want
* Matthias Klose , 2010-01-15, 14:58:
symlinks / private directories if given Python version is installed
(dpkg -L output will be used to detect which files need byte compilation,
directories without __init__.py file will be skipped),
IOW, you want to skip modules that are not a part of a packa
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
[Piotr Ożarowski, 2010-01-15]
> [Luca Falavigna, 2010-01-15]
> > Piotr Ożarowski ha scritto:
> > > byte compilation will not fail as it was already tested at build time,
> >
> > What about cases when code is no longer supported in a given Python
> > release? I think of "except YourFavouriteExc
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 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
[Jakub Wilk, 2010-01-15]
> * 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
[Luca Falavigna, 2010-01-15]
> Piotr Ożarowski ha scritto:
> > * no need for helper in Depends and Build-Depends - I want dh_python and
> > pycompile/pyclean to be shipped in python packages,
>
> It is not clear to me how to achieve this.
Matthias promised to lend me some space in python packag
* 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,
directories without __init__.py file will be sk
Piotr Ożarowski ha scritto:
> * no need for helper in Depends and Build-Depends - I want dh_python and
> pycompile/pyclean to be shipped in python packages,
It is not clear to me how to achieve this.
> * broken modules that use __file__ incorrectly will work without problems,
OK, I'd still war
Here's updated dh_python proposal. Main change since my last mail:
pycompile/pyclean will no longer search for files to compile/remove
in public directories as Matthias will fix #552595 using triggers so I don't
have to care about pycentral bugs anymore and dpkg -L seems to be fast enough
to be use
FTR: Joss and few other maintainers (whose opinion I care about) didn't
like my proposal (mainly due to binNMUs for arch:all packages) so I'm not
working on this new tool. I planed to start working on it once we'll
agree how it should look like. There's no consensus so I'm focusing on
preparing all
Kumar Appaiah wrote:
> On Tue, Aug 04, 2009 at 12:00:09PM -0400, anatoly techtonik wrote:
>> Now about the proposal (from newcomer's point of view):
>> dh_python is a shell script -- I have a strong belief that Python
>> package automation scripts should be written in Python, there is no
>> need to
[Matthias Klose, 2009-08-20]
> On 03.08.2009 19:16, Piotr Ożarowski wrote:
> >* about lack of XS-Python-Version and debian/pyversions
> > - if available, both previous places will be used to get
> > minimum/maximum required Python version, it will complicate
> > detection of packages that
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
[anatoly techtonik, 2009-08-04]
> Before discussing your proposal I would really appreciate if somebody
> from insiders could describe situation in Debian Python in all
> possible detail including the history of development. I believe that
> this piece of work is absolutely necessary, because the p
On Tue, Aug 04, 2009 at 12:00:09PM -0400, anatoly techtonik wrote:
> Now about the proposal (from newcomer's point of view):
> dh_python is a shell script -- I have a strong belief that Python
> package automation scripts should be written in Python, there is no
> need to learn bashes when you prog
Hello, Piotr.
In short - your post is long. Brain is limited. Better place an
overview in wiki and discuss in parts.
Before discussing your proposal I would really appreciate if somebody
from insiders could describe situation in Debian Python in all
possible detail including the history of devel
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 all files provided by packages is something we
My attempt to merge python-central and python-support failed few months ago, so
here's another proposal to improve the Python situation in Debian. It's nothing
new
actually, just a compilation of previous Matthias' and Joss' ideas and few of my
own.
The main idea is to ship symlinks (not .pyc fil
Joey Hess writes:
> I don't particularly mind that you've chosen to NMU debhelper. However,
> I can't guarantee that I will preserve the interfaces that you've added
> to dh_python in a backwards compatible way when I get around to looking
> at it.
>
> (FWIW, I began ignoring this issue when the p
Le mardi 13 juin 2006 à 15:23 -0400, Joey Hess a écrit :
> (FWIW, I began ignoring this issue when the politics and constant
> advocacy and pressure became too annoying to bother with, and I expect
> to ignore it for at least another couple of weeks. Unfortunatly that
> means that to avoid either t
I don't particularly mind that you've chosen to NMU debhelper. However,
I can't guarantee that I will preserve the interfaces that you've added
to dh_python in a backwards compatible way when I get around to looking
at it.
(FWIW, I began ignoring this issue when the politics and constant
advocacy
Coin,
Raphael Hertzog <[EMAIL PROTECTED]> writes:
> Without any answer from you, I might upload it right before dinstall
> (depending on the opinion of other involved people).
This is perfectly reasonnable.
--
Marc Dequènes (Duck)
pgpU3t0AM8OF7.pgp
Description: PGP signature
On Mon, 12 Jun 2006, Raphael Hertzog wrote:
> On Mon, 12 Jun 2006, Raphael Hertzog wrote:
> > I would love to have this fixed by today's dinstall. That's why I
> > prepared the attached NMU, please just send an OK and I'll upload it (of
> > course, feel free to do it yourself in a maintainer upload
On Mon, 12 Jun 2006, Raphael Hertzog wrote:
> I would love to have this fixed by today's dinstall. That's why I
> prepared the attached NMU, please just send an OK and I'll upload it (of
> course, feel free to do it yourself in a maintainer upload).
>
> Without any answer from you, I might upload
On 10/06/2006 Joe Wreschnig wrote:
> > Please reconsider. If you don't integrate that version now, we'll most
> > probably do the switch to python2.4 in the next days and we'll replace
> > dh_python calls by dh_python2 calls (integrated for example in the python
> > package) or we'll remove call to
* Andreas Barth ([EMAIL PROTECTED]) [060611 10:13]:
> * Raphael Hertzog ([EMAIL PROTECTED]) [060611 10:00]:
> > What is slowing our progress is the refusal to let the time decide between
> > python-central and/or python-support. There's no consensus here and if you
> > need to make a choice, your o
* Raphael Hertzog ([EMAIL PROTECTED]) [060611 10:00]:
> What is slowing our progress is the refusal to let the time decide between
> python-central and/or python-support. There's no consensus here and if you
> need to make a choice, your only possibility is to request the technical
> committee to m
On Sun, 11 Jun 2006, Dafydd Harries wrote:
> Ar 10/06/2006 am 21:50, ysgrifennodd Raphael Hertzog:
> > I have written dh_pycentral and dh_pysupport which will take care of the
> > byte-compilation of the modules and integration with the respective tools.
> > Those should be integrated in their resp
Ar 10/06/2006 am 21:50, ysgrifennodd Raphael Hertzog:
> I have written dh_pycentral and dh_pysupport which will take care of the
> byte-compilation of the modules and integration with the respective tools.
> Those should be integrated in their respective packages (after review by
> their maintainer
On Sat, 10 Jun 2006, Raphael Hertzog wrote:
> > I appreciate your work, but I am not comfortable supporting two
> > competing implementations in debhelper.
>
> Please reconsider. If you don't integrate that version now, we'll most
> probably do the switch to python2.4 in the next days and we'll re
On Sat, 2006-06-10 at 09:08 +0200, Raphael Hertzog wrote:
> On Fri, 09 Jun 2006, Joey Hess wrote:
> > Raphael Hertzog wrote:
> > > Because Matthias and Josselin do not (or can't or don't want to) work
> > > together. I tried my best to fill the gap. :-/
> >
> > I appreciate your work, but I am not
On Fri, 09 Jun 2006, Joey Hess wrote:
> Raphael Hertzog wrote:
> > Because Matthias and Josselin do not (or can't or don't want to) work
> > together. I tried my best to fill the gap. :-/
>
> I appreciate your work, but I am not comfortable supporting two
> competing implementations in debhelper.
Raphael Hertzog wrote:
> Because Matthias and Josselin do not (or can't or don't want to) work
> together. I tried my best to fill the gap. :-/
I appreciate your work, but I am not comfortable supporting two
competing implementations in debhelper.
Sorry.
--
see shy jo
signature.asc
Descriptio
Le vendredi 09 juin 2006 à 14:07 +0200, Raphael Hertzog a écrit :
> OK, I did test it myself finally this morning (with regular feedback from
> Matthias as well). It leads me to some corrections so please find an
> updated (and final!) dh_python in attachment.
>
> Matthias and Josselin, please sa
Raphael Hertzog writes:
> On Fri, 09 Jun 2006, Raphael Hertzog wrote:
> > This dh_python depends neither on python-central nor on python-support but
> > it
> > can work with both.
> >
> > It will use python-central if it appears in a build-dependency.
> > It will use python-support if it detects
On Fri, 09 Jun 2006, Raphael Hertzog wrote:
> This dh_python depends neither on python-central nor on python-support but it
> can work with both.
>
> It will use python-central if it appears in a build-dependency.
> It will use python-support if it detects /usr/share/python-support/$package.
>
>
On Thu, 08 Jun 2006, Raphael Hertzog wrote:
> This dh_python will use python-central for any binary package with a
> XB-Python-Version: field. There's no optional python-support either.
>
> So anyone unhappy with python-central should really come up with another
> dh_python implementation RSN.
OK
47 matches
Mail list logo
