At 8:29 PM -0800 2/8/06, Bill Janssen wrote:
>I've made up a sample page, at
>http://bill.janssen.org/new-macpython-page.html.
>
>This is the kind of thing I'd like to see replace the page at
>http://www.python.org/download/download_mac.html.
Bill,
As the sort of somewhat sophisticated novice py
At 1:20 PM -0800 2/9/06, Bob Ippolito wrote:
>py2app is the solution for application packaging, and you must use
>it with a third party Python installation (e.g. Python 2.4.1) in
>order to come up with something that's redistributable and robust.
>If you happen to use the system Python, then
At 1:39 PM -0800 2/9/06, Bill Janssen wrote:
>Great idea, Rodney. I think we probably need a number of pages like
>this, kind of an FAQ set. I think the main page should just cover one
>or two things (how to run python, how to upgrade), and lots of
>pointers to these pages. Each of these should
At 9:51 AM -0800 2/10/06, Bill Janssen wrote:
>The problem is that there are many kinds of "new users".
>
This is true. The trick, in my view, is to make sure to define terms
when they are first used. That way, the actual beginners have a
chance of following along and the more experienced "new u
At 11:58 AM -0800 2/10/06, Christopher Barker wrote:
>Rodney Somerstein wrote:
>>. It would be really nice to have a more basic introduction to what
>>py2app actually does.
>
>Why don't you write that, put it in the Wiki, then ask this list for
>technical review. Tha
I didn't notice anyone mentioning this on previous discussions, but
currently, if you click the download link on the left side of the
main python.org site, it takes you to a page that states this about
the Mac version of Python:
Python 2.3 OS X 10.2 installer (requires admin privileges -- see
As the title of this message asks, which Python should I use? And
why? From following discussions here, I know why I don't want to use
the built in Apple Python.
So, that leaves 2 choices that both seem good, the macpython
framework build and ActiveState. The main reason that I would want to
u
Thanks for the answer, Bob, and thanks for the work on the Universal
build, Ronald. If someone could answer my other questions as well, I
would really appreciate it.
As a beginner, what does having a working readline actually mean to
me? If I'm not building command line apps do I need that for
Thanks for your extensive answer, Bob. I will definitely go with the
universal build given what you have said, just to facilitate getting
help with any problems I run into. As for py2app not working with
that yet, I'm still a long way from having anything ready to package
anyway, so that isn't
(Lots of stuff about non-Universal builds of stuff and other comments
from various people removed...)
Luckily for me, I'm still a good ways away from needing to actually
create a standalone app. That is just my ultimate goal. If there
isn't a universal build of py2app by the time that I'm ready
, it is definitely more convenient to just
double-click. I am using IDLE because I have been working my way through the
O'Reilly Learning Python book at a glacial pace over the last year or more and
it is nice to have a simple Python-aware interactive editor.
-Rodney
--
Rodney Somer
Ronald Oussoren wrote:
>Could you open Console.app, clear the log and then try to start IDLE
>again? Hopefully IDLE runs into a problem that gets written to the
>console log.
Here is what I see when I double-click on IDLE:
Traceback (most recent call last):
File "/Applications/MacPython
2.
gt;>Eclipse
>>SPE
>>Jedit
>>ScrIDE
>>
>>
>>Assorted *nix editors: emaca, VIm, etc, etc.
>>
>>or look here:
>>
>>http://wiki.python.org/moin/PythonEditors
>>
>>-Chris
--
Rodney SomersteinAlways remember that
h, IDLE is working for me again and I'm happily testing
various commands and testing out answers to the end of section
questions in Learning Python.
-Rodney
--
Rodney SomersteinAlways remember that you are unique...
[EMAIL PROT
Given the recent release of Python 3.0, I've been surprised to see no
mention of a Mac release of this. Is anyone working on an official
release? If so, is there an expected release date?
Thanks,
-Rodney
___
Pythonmac-SIG maillist - Pythonmac-SIG@p
On Tuesday, May 24, 2010, Aahz wrote:
If you care about the Mac (particularly in terms of being able to use
PyObjC and/or py2app), stick with 2.x for now. Otherwise, it doesn't
matter much which exact version of 3.x you use.
This brings up a question for me as to what the state of Python is on
At 11:17 AM -0700 5/25/10, Christopher Barker wrote:
Honestly, I don't know if the Mac is in any poorer position with
regard to Python 3 as any other platform.
NONE of the major packages I use have been ported to Py3 on any
platform: numpy, SciPy, wxPython. Many of those are well supported
on
At 10:08 PM +0200 5/25/10, Ronald Oussoren wrote:
Python 3.1.2 works fine on OSX. There is an issue with building
extensions on OSX 10.6, but that will be fixed in 3.1.3.
PyObjC in the repository works with python 3 and I'm working towards
a release. I haven't looked into py2app yet. With some
18 matches
Mail list logo
