Ronald Oussoren wrote:
> Setting the working directory to the directory containing the script
> would be more useful.
I'm not so sure. That's a bad habit from the old MacOS and Windows.
$HOME is an excellent choice for the default working directory.
It might make sense to add the directory con
On Jul 24, 2006, at 9:31 AM, Christopher Barker wrote:
> Ronald Oussoren wrote:
>> Setting the working directory to the directory containing the script
>> would be more useful.
>
> I'm not so sure. That's a bad habit from the old MacOS and Windows.
> $HOME is an excellent choice for the default w
On Jul 24, 2006, at 6:31 PM, Christopher Barker wrote:
> Ronald Oussoren wrote:
>> Setting the working directory to the directory containing the script
>> would be more useful.
>
> I'm not so sure. That's a bad habit from the old MacOS and Windows.
> $HOME is an excellent choice for the default w
Ronald Oussoren wrote:
> Why's that? The directory that contains the script is a lot more useful
> for most scripts.
Bob Ippolito wrote:
> No, it's not. There are approximately zero scripts that expect this
> behavior.
Most "scripts" I've ever used are used from the command line, and the
worki
On Jul 24, 2006, at 11:17 AM, Christopher Barker wrote:
> Ronald Oussoren wrote:
>> Why's that? The directory that contains the script is a lot more
>> useful
>> for most scripts.
> Bob Ippolito wrote:
>> No, it's not. There are approximately zero scripts that expect this
>> behavior.
>
> Most
On Jul 24, 2006, at 8:52 PM, Bob Ippolito wrote:
>
> On Jul 24, 2006, at 11:17 AM, Christopher Barker wrote:
>
>> Ronald Oussoren wrote:
>>> Why's that? The directory that contains the script is a lot more
>>> useful
>>> for most scripts.
>> Bob Ippolito wrote:
>>> No, it's not. There are approxi
I'm absolutely new in the mac's world.I just bought a MacBook.I'am trying to install Python 2.4 on it apart to the preinstalled 2.3version.I read on the net that I'd to install firstUniversal-MacPython-2.4.3-2006-04-07.dmg
and then to patch it with TigerPython24Fix-r2Python 2.4 's installation was
On Jul 24, 2006, at 1:14 PM, IloChab wrote:
> I'm absolutely new in the mac's world.
> I just bought a MacBook.
> I'am trying to install Python 2.4 on it apart to the preinstalled 2.3
> version.
>
> I read on the net that I'd to install first
> Universal-MacPython-2.4.3-2006-04-07.dmg
> and then
Kevin Reid, http://homepage.mac.com/kpreid/, has just released v1.2
of plist.py which supports reading and writing xml1 plist files. It
converts the xml1 plist files to Python standard types such as
dictionary, list, etc. It will also write out properly structured
Python types as plist xm
On Jul 24, 2006, at 1:38 PM, Robert White wrote:
> Kevin Reid, http://homepage.mac.com/kpreid/, has just released v1.2
> of plist.py which supports reading and writing xml1 plist files. It
> converts the xml1 plist files to Python standard types such as
> dictionary, list, etc. It will also wri
Hi All,
I've recently upgraded to the Universal Build, since 2.4.3 seems to be
needed for the most recent version of numpy.
Further, the universal build is made with gcc 4.0.1, and seems to need
that for compiling extensions.
This does present a few problems: numpy actually has a fairly obscur
On Jul 24, 2006, at 3:55 PM, Andrew Jaffe wrote:
> I've recently upgraded to the Universal Build, since 2.4.3 seems to be
> needed for the most recent version of numpy.
>
> Further, the universal build is made with gcc 4.0.1, and seems to need
> that for compiling extensions.
>
> This does presen
On 24 Jul 2006, at 23:59, Bob Ippolito wrote:
>
> On Jul 24, 2006, at 3:55 PM, Andrew Jaffe wrote:
>
>> I've recently upgraded to the Universal Build, since 2.4.3 seems
>> to be
>> needed for the most recent version of numpy.
>>
>> Further, the universal build is made with gcc 4.0.1, and seems
Andrew Jaffe wrote:
> This does present a few problems: numpy actually has a fairly obscure
> bug on OSX with gcc 4.
Is this in the bug tracker and on the table for fixing before 1.0 comes
out? I hope so -- gcc4.* is not exactly bleeding edge anymore.
> More importantly, g77 and gcc 4.0 don't s
IloChab wrote:
> Could it be something related to the Intel core of my Mac?
> On the page from where I downloaded the fix
> http://pythonmac.org/packages/legacy.html
Note the URL in that page: "legacy". That means this is old stuff you
don't need if you have a new system.
Bob, I do have one sugg
>>> When a script is installed somewhere central, like /usr/local/bin,
>>> that's really all that makes sense.
>>
>> That's clearly irrelevant, because people aren't going to be double-
>> clicking on files that you have to do "magic incantations" to even
>> see from Finder.
Fair enough, but what
On 25/07/2006, at 6:20 AM, Christopher Barker wrote:
>> Setting the working directory to the directory containing the
>> script would be more useful.
It really is a bad idea to write into software directories of any
sort. They should be able to be write protected for security.
>
> I'm not s
Good point Jim -
I just now realized this myself.
So I re-compiled/installed Python2.4 - and reverted back
to fltk version 1.1 (instead of 1.1.1), as suggested by
Andreas Held himself.
Now I'm getting these messages when trying to build pyfltk:
cc1plus: warning: command line option "-Wstrict-p
18 matches
Mail list logo
