Ned Deily writes:
> In article
> ,
> Benjamin Kaplan wrote:
>> On Sat, May 9, 2009 at 4:30 AM, Raoul Gough
>> wrote:
[snip]
>> > So did something go wrong with the installer, or is it all
>> > supposed to work somehow differently?
>>
>> Because Python 3 breaks compatibility with Python 2, th
In article
,
Benjamin Kaplan wrote:
> On Sat, May 9, 2009 at 4:30 AM, Raoul Gough wrote:
> > I just installed MacPython 3.0.1 (woot!) but the installer didn't seem
> > to do an absolutely complete job. According to the ReadMe.txt, "The
> > installer puts [...] command-line tools in /usr/local/bi
On Sat, May 9, 2009 at 4:30 AM, Raoul Gough wrote:
> I just installed MacPython 3.0.1 (woot!) but the installer didn't seem
> to do an absolutely complete job. According to the ReadMe.txt, "The
> installer puts [...] command-line tools in /usr/local/bin [...]". This
> didn't happen - even after th
I just installed MacPython 3.0.1 (woot!) but the installer didn't seem
to do an absolutely complete job. According to the ReadMe.txt, "The
installer puts [...] command-line tools in /usr/local/bin [...]". This
didn't happen - even after the install reported Success, there were no
python files or sy
