Ed,
Quote:
Originally Posted by edembowski
I'm very glad to hear that you're working now!
|
Thanks.
Quote:
Originally Posted by edembowski
The .pyw extension stands for 'Python for Windows' and it goes back to Microsoft's old limitation of 3 letter file extensions. The limit is no longer there, but it's kept that way for historical reasons. Macs (and Unix in general) uses .py
|
Makes sense!
Quote:
Originally Posted by edembowski
The key is stored in a plain text file in clear text. Howard's PM should sort you out.
|
It did. I have been PM'ing back and forth with him in an effort to get the necessary commands working in my Terminal shell, and I have also asked
adullday for his permission to incorporate the commands in an AppleScript script that I would make available to one and all through a blog post. If all that works out, then the script would be capable of putting an
adept_key.der file for the user in whatever folder the Mac user designates.
Quote:
Originally Posted by edembowski
A dependency for installation is the file to install. The installer knows how to build it, so if you try to install without building, it will build automagically.
|
So
that's why I found doing the build before the install was unnecessary!
Quote:
Originally Posted by edembowski
Your mileage may vary. I've done the install and it keeps 2.5 as the default python. Maybe there's a preference pane that controls it, I haven't checked.
|
It may be desirable at some point for someone to figure this out, since it is a possible pitfall for the unwary and uninitiated. I also found that I had to manually change what gets opened for a double-click in Finder on a
.py script file: Python Launcher, not IDLE. (For lurkers: this is done by doing Get Info for a .py file and selecting
Open with: Python Launcher, and optionally clicking the
Change All ... button if you want the behavior to apply to
all .py files.) Also, the Preferences pane for Python Launcher needed to be changed to uncheck
Run in a terminal window. Otherwise, every time a
.py script is double-clicked, Python Launcher is invoked and in turn fires up Terminal needlessly. Of course, if you are using the command-line interface in Terminal and not Finder double-clicks, you can circumvent all such concerns.
Quote:
Originally Posted by edembowski
I've never tried dragging things to the terminal window, it seems fishy to me. From the shell, I just `cd` to the right directory and take it from there.
|
Actually, one way to 'cd' to the right directory is to enter 'cd ' and drag the folder for the directory from Finder to the Terminal window. It is a matter of personal preference whether a user wants to pollute the purity of the CLI by doing so, admittedly.
Thanks for all your help, Ed.
Eric