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
6 matches
Mail list logo
