Jesse Noller [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
On Tue, Aug 19, 2008 at 1:28 PM, Bill Janssen [EMAIL PROTECTED] wrote:
My understanding is that if there is a system Python, you shouldn't
change it. Ever.
Huge, big, honkin' +1 from me on that. Besides, for a system
Bill Janssen wrote:
I strongly recommend that we *NOT* make macports.org the main,
official Mac OS X version of Python. Secondary is fine, but not
primary. Macports is what the name says: it's a system of Mac ports of
Linux packages, mostly command-line only.
I agree with David about this.
Leonardo Santagada wrote:
-1 to use mac ports python as the base python
On 18/08/2008, at 22:18, Bill Janssen wrote:
The official Mac Python should be an OS X application, with an icon,
living in /Applications, ideally with a Mac-standard editor app (the
2.5.1 I have has IDLE), etc.
No,
On Aug 19, 2008, at 3:45 AM, [EMAIL PROTECTED] wrote:
I *thought* (relative Mac newbie), the standard advice was that if you
want to install extension modules then you should install your own
version
of Python and not mess with the system version.
My understanding is that if there is a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Aug 19, 2008, at 8:51 AM, Fred Drake wrote:
My understanding is that if there is a system Python, you shouldn't
change it. Ever.
Huge, big, honkin' +1 from me on that. Besides, for a system Python,
you want your distribution to manage
On Tue, Aug 19, 2008 at 8:51 AM, Fred Drake [EMAIL PROTECTED] wrote:
On Aug 19, 2008, at 3:45 AM, [EMAIL PROTECTED] wrote:
I *thought* (relative Mac newbie), the standard advice was that if you
want to install extension modules then you should install your own version
of Python and not mess
[Removed pydotorg from the recipients; this has nothing to do with the
website.]
On Aug 19, 2008, at 10:51 AM, Jesse Noller wrote:
Just to add to this - with the advent of PEP 370[1], we now have the
ability to use per-user site-packages directories. This neatly
sidesteps the problem (for the
I've certainly heard many tales of Mac users coming to grief because
they decided to overwrite their system Python, or tried to be clever and
run multiple interpreters (which is usually somewhat less disastrous).
I guess this underlines the fact that Apple don't really want the hoi
My understanding is that if there is a system Python, you shouldn't
change it. Ever.
Huge, big, honkin' +1 from me on that. Besides, for a system Python,
you want your distribution to manage packages, not setuptools,
otherwise you confuse -- and probably break -- your system.
I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Aug 19, 2008, at 1:28 PM, Bill Janssen wrote:
My understanding is that if there is a system Python, you shouldn't
change it. Ever.
Huge, big, honkin' +1 from me on that. Besides, for a system Python,
you want your distribution to manage
On 19-Aug-2008, at 19:28 , Bill Janssen wrote:
My understanding is that if there is a system Python, you shouldn't
change it. Ever.
Huge, big, honkin' +1 from me on that. Besides, for a system Python,
you want your distribution to manage packages, not setuptools,
otherwise you confuse --
On Tue, Aug 19, 2008 at 1:28 PM, Bill Janssen [EMAIL PROTECTED] wrote:
My understanding is that if there is a system Python, you shouldn't
change it. Ever.
Huge, big, honkin' +1 from me on that. Besides, for a system Python,
you want your distribution to manage packages, not setuptools,
On Aug 18, 2008, at 5:42 PM, Steve Holden wrote:
Someone told me the other day that macports made for difficult
installs, but not being a Mac user I wasn't in a position to
evaluate the advice.
Not being a Mac user either, I've been using Mac OS X for about a year
now for most of my
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Aug 18, 2008, at 6:13 PM, Fred Drake wrote:
On Aug 18, 2008, at 5:42 PM, Steve Holden wrote:
Someone told me the other day that macports made for difficult
installs, but not being a Mac user I wasn't in a position to
evaluate the advice.
Guido van Rossum wrote:
Alternatively, I just got mail from Bob Ippolito indicating that he'd
be happy to hand over the domain to the PSF. It's got quite a bit more
on it than Python distros, and it's a fairly popular resource for Mac
users I imagine. However macports.org seems to have more
On Mon, Aug 18, 2008 at 3:41 PM, Barry Warsaw [EMAIL PROTECTED] wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Aug 18, 2008, at 6:13 PM, Fred Drake wrote:
On Aug 18, 2008, at 5:42 PM, Steve Holden wrote:
Someone told me the other day that macports made for difficult installs,
but
I strongly recommend that we *NOT* make macports.org the main,
official Mac OS X version of Python. Secondary is fine, but not
primary. Macports is what the name says: it's a system of Mac ports of
Linux packages, mostly command-line only.
I agree with David about this.
The official Mac
Bill Janssen wrote:
I strongly recommend that we *NOT* make macports.org the main,
official Mac OS X version of Python. Secondary is fine, but not
primary. Macports is what the name says: it's a system of Mac ports of
Linux packages, mostly command-line only.
I agree with David about this.
-1 to use mac ports python as the base python
On 18/08/2008, at 22:18, Bill Janssen wrote:
The official Mac Python should be an OS X application, with an icon,
living in /Applications, ideally with a Mac-standard editor app (the
2.5.1 I have has IDLE), etc.
No, probably not. Frankly, I
19 matches
Mail list logo
