On Sat, Sep 06, 2003 at 09:35:07AM +0200, Matthias Klose wrote:
> On Thu, 3 Jul 2003 01:38:23 +0100 you wrote:
>
> > PyQt 3.7 is supposed to be released this weekend. Then I'll updated
> > fixed packages.
>
> this seems to be a long weekend :-( in the meantime pyQt 3.8 was
> released. would you m
On Fri, Aug 08, 2003 at 11:05:09AM +0200, Matthias Klose wrote:
> Ricardo Javier Cardenes Medina writes:
> > Of course, all this require manual handling from the user. What I was
> > proposing would require a whole PEP and some reasonable design and
> > implementation, etc, s
On Fri, Aug 08, 2003 at 09:03:05AM +0200, Alexandre Fayolle wrote:
> You always can copy the .py[co] files in
> /usr/lib/python2.X/site-packages at install time. Since these directory
> come before /usr/lib/site-python in the default sys.path, the compiled
> modules will be used on import.
>
> N
On Thu, Aug 07, 2003 at 12:58:25PM +1000, Donovan Baarda wrote:
> Anyone else agree?
I see no problem, aside from performance for those users not using the
default version, but since this is only a "load time" problem, it
shouldn't be more than a little annoyance. I suppose that really picky
users
On Thu, May 30, 2002 at 02:46:46PM +0400, Wartan Hachaturow wrote:
> As you may noticed ;), most of the Debian packages now use Perl in their
> build-time and install-time scripts.
> Why is this? Perhaps, we can make some version of python to be
> "default" (Just like we do now with 2.1), and make
On Thu, May 23, 2002 at 04:34:18AM -, Moshe Zadka wrote:
>
> > 1a) as 1), but also provide foo symlink for python (default).
>
> this makes senseI can just put the symlink in python2.1-foo-bin and
> move the symlinks when a python default change.
Or you can use the update-alternatives to
On Tue, Nov 27, 2001 at 03:18:08AM -0600, Colin Watson wrote:
> > or
> >
> > libsip.so.2.python2.1.x.y... ugly! it is even possible?
>
> That sounds best to me in the absence of any better coordination from
> upstream, or being able to use a single libsip. I agree that it's ugly,
> though.
>
On Tue, Nov 27, 2001 at 02:37:58AM +1100, Donovan Baarda wrote:
> On Mon, Nov 26, 2001 at 02:52:51PM +0000, Ricardo Javier Cardenes wrote:
> Maybe I'm an idiot and I don't fully understand the problem... but what's
> the problem?
Probably I explained bad the problem, or
I'm re-packaging 'sip' and 'python-pyqt' to make them comply the new
Policy, but I've just found a problem. Let me explain it a bit:
- sip is a tool that helps creating Python wrappers over C++ classes.
It parses a .sip (kind of .i - swig) file, and generates .cpp and .py
You end with a .p
On Sun, Oct 21, 2001 at 10:58:01PM +1300, Carey Evans wrote:
> Donovan Baarda <[EMAIL PROTECTED]> writes:
>
> (Actually 60, but gimp-python also depends on python-base (<< 1.6.0)).
>
> Packages that depend on python:
>grep-dctrl -FDepends -e 'python([ ,]|$)' Packages
I maintain one of those
On Mon, Sep 17, 2001 at 07:33:26PM -0700, Neil Schemenauer wrote:
> 1.2. Module Path
>
>
> Python searches a number of directories for modules. The module
> search path for Debian has been ordered to include these locations at
> the beginning of the path in the fol
11 matches
Mail list logo
