On Thu, 5 Jul 2001, Bruce Sass wrote:
> The problem with both the FAQ and Debian's Python is that they have
> been assuming nobody will ever have more than one Python on the
> system, and it will always be as recent as the most recent program...
> as long as the language is backwards compatible the
On Thu, 5 Jul 2001, D-Man wrote:
> On Thu, Jul 05, 2001 at 06:43:08PM +0100, Aquarius wrote:
> | In article <[EMAIL PROTECTED]> you wrote:
> | > I just browsed /usr/bin and /usr/sbin, and indeed there are plenty of
> | > scripts that use "#!/usr/bin/env python". If we consider the possibility
> | >
Aquarius wrote:
> Especially since "#!/usr/bin/env python" is recommended in the Python
> FAQ (section 4.63 --
> http://www.python.org/cgi-bin/faqw.py?req=show&file=faq04.063.htp). Is
> it bad to use in general, or just bad to use on Debian systems?
Depends. If your writing a script or program to
On Thu, Jul 05, 2001 at 06:43:08PM +0100, Aquarius wrote:
| In article <[EMAIL PROTECTED]> you wrote:
| > I just browsed /usr/bin and /usr/sbin, and indeed there are plenty of
| > scripts that use "#!/usr/bin/env python". If we consider the possibility
| > that somebody installs non-compatible Pyth
In article <[EMAIL PROTECTED]> you wrote:
> I just browsed /usr/bin and /usr/sbin, and indeed there are plenty of
> scripts that use "#!/usr/bin/env python". If we consider the possibility
> that somebody installs non-compatible Python versions in the path, then
> these are bugs in that packages. T
Gregor Hoffleit wrote:
> Pure Python packages not necessarily would need to be rebuilt (if the
> code was cross-version compatible).
It almost always is. Python tries very hard to remain source compatible
across releases. I've been using Python for 9 years and can only think
of one case were my
Gregor Hoffleit wrote:
> Binary extension modules depend on the version of Python that they were
> compiled against (a different micro version should be ok, AFAIK).
That's right. Maybe I don't understand the mess we are in now. Can you
explain exactly what it is?
As I understand it, we want to
On Thu, Jul 05, 2001 at 05:33:37PM +0200, Gregor Hoffleit wrote:
> On Thu, Jul 05, 2001 at 07:56:57AM -0700, Neil Schemenauer wrote:
> > > That's our current setup (well-behaved packages should have a dependency
> > > on "python-base >= 1.5, python-base << 1.6"). Look at the mess we're now
> > > ru
On Thu, Jul 05, 2001 at 07:56:57AM -0700, Neil Schemenauer wrote:
> Gregor Hoffleit wrote:
> > Sorry ? What problems do you have installing Python 2.1 in /usr/local on
> > a Debian system ?
>
> Sometimes /usr/local/bin/python is used instead of /usr/bin/python. For
> example, dput uses "#!/usr/bi
Gregor Hoffleit wrote:
> Sorry ? What problems do you have installing Python 2.1 in /usr/local on
> a Debian system ?
Sometimes /usr/local/bin/python is used instead of /usr/bin/python. For
example, dput uses "#!/usr/bin/env python". Also, its postinst script it
does:
python -c 'from compil
On Thu, Jul 05, 2001 at 07:13:54AM -0700, Neil Schemenauer wrote:
> Gregor Hoffleit wrote:
> > Until now I had the impression that in general it's not necessary to
> > have more than one Python version on your machine at the same time
> > (except perhaps you're a Python core developer). Feedback fr
Gregor Hoffleit wrote:
> Until now I had the impression that in general it's not necessary to
> have more than one Python version on your machine at the same time
> (except perhaps you're a Python core developer). Feedback from
> python-dev though was that it's definitely necessary to allow and
> s
On Wed, 4 Jul 2001, Gregor Hoffleit wrote:
> First of all the good news: You have managed to talk me into making the
> big step, and going right to the 2.1.1 CVS branch. Thomas Wouters
> (release czar for Python 2.1.1) assured me that 2.1.1 will be released
> before the freeze, and Guido heavily s
On Wed, Jul 04, 2001 at 09:00:06PM -0500, Chris Lawrence wrote:
> - python-* should provide a "Standard" Python for each Debian
> release. 2.1.1 seems a sensible target for woody. These packages
> should be invoked by /usr/bin/python and /usr/bin/pythonx.y
If we are going to have multiple ve
14 matches
Mail list logo
