On Fri, Jan 21, 2011 at 1:40 PM, Bill Janssen wrote:
> Charles Hartman wrote:
>
> > it would seem to be short-sighted for anyone interested in Python on
> > the Mac not to support py2app as fully as possible.
>
> You calling me short-sighted, Charles?
>
> That's OK -- it's true, you know; I've b
Charles Hartman wrote:
> it would seem to be short-sighted for anyone interested in Python on
> the Mac not to support py2app as fully as possible.
You calling me short-sighted, Charles?
That's OK -- it's true, you know; I've been wearing thick glasses since
I was a kid :-). But I don't know t
On 1/20/11 4:51 PM, Adam Morris wrote:
I want one programming language that lets me solve my real
problems.
That to me, is what Python embodies.
yup -- it is applicable to a VERY wide range of problems.
But I'm still confused on some major points on what it offers.
I use Xcode and Coco
We shouldn't lose sight of the fact that the people we're talking about who
need to build Python programs as apps -- several of whom have responded here
-- don't typically want to confine those apps to the world of Macs. Python
is a great language in which to build cross-platform (LOTS of platform
Adam Morris wrote:
> >By the way, Python is more than "just another good scripting
> >language". I build large systems with it. I do (rarely) write Mac
> >"applications" with Python. I use Xcode and Cocoa-Python, and
> >IMO it works great. Is that using py2app "under the covers"? This
> >is a
This python development convo has been by far the most informative so
far. I'm coming at this from very much a hobbyist position. I'm a
teacher and I want one programming language that lets me solve my real
problems. I also want the same language to be able to do native Mac
stuff too, if I ever hav
In article <69949.1295543...@parc.com>, Bill Janssen
wrote:
> Christopher Barker wrote:
>
> > > and certainly the majority of those who need any help.
> >
> > I think that's key -- Bill's approach is fine one for some users, but
> > not what I"d recommend to newbies that aren't sure how to se
Chris Weisiger writes:
> In short, if you are coding for other people who are not themselves
> programmers and who use OSX, then you want py2app.
I definitely agree with this. Py2app lets my self-contained Python
apps conform to the platform norm that users are expecting. In that
respect it's
Christopher Barker wrote:
> > and certainly the majority of those who need any help.
>
> I think that's key -- Bill's approach is fine one for some users, but
> not what I"d recommend to newbies that aren't sure how to set a PATH.
Hmmm. My experience is that those are exactly the folks who get
On Thu, Jan 20, 2011 at 8:56 AM, Christopher Barker
wrote:
> On 1/19/11 9:11 PM, Charles Hartman wrote:
>
>>Do I need/want to use py2app to distribute my app(s)?
>>Never happens.
>>
>
> But this is where Bill J's use-case departs drastically from those of
>> many users, perhap
On 1/19/11 9:11 PM, Charles Hartman wrote:
Do I need/want to use py2app to distribute my app(s)?
Never happens.
But this is where Bill J's use-case departs drastically from those of
many users, perhaps most, and certainly the majority of those who need
any help.
I'm not s
On Wed, Jan 19, 2011 at 2:10 PM, Christopher Barker
wrote:
>
>
> Do I need/want to use py2app to distribute my app(s)?
>>>
>>
>> Never happens.
>>
>
> fair enough.
>
But this is where Bill J's use-case departs drastically from those of many
users, perhaps most, and certainly the majority of th
On Wed, Jan 19, 2011, Christopher Barker wrote:
>
> OK -- well, I'd say the solution to that is simple: DON'T DO THAT.
> We say time and time again that you should NEVER mess with Apple's
> python.
Just to repeat for emphasis: NEVER mess with ANYONE'S system python.
Doesn't matter whether it's Mac
NOTE:
I'm not trying to persuade Bill of anything -- he's clearly found a
method that works well for him, but for future googlers, I think a few
clarifications are in order:
On 1/18/11 4:29 PM, Bill Janssen wrote:
Bill -- I'm really curious what issues you've had --
In general, there are
On 17/01/2011 22:41, Tony Cappellini wrote:
I do want 2.7 because it's a requirement at work.
I want to have the same versions & packages to avoid compatibility issues.
I can put Python2.7 in a different directory and leave 2.6 there but I
want the 2.7 installation
to be the default one.
For
Christopher Barker wrote:
> On 1/17/11 9:17 AM, Bill Janssen wrote:
> >> And- I want to update the default python that came om my macbook pro to
> >> 2.7.
> >> Should I do install that from Python.org?
> >
> > My advice? I've never had good luck trying to "update" the default
> > Python that co
On 1/17/11 9:17 AM, Bill Janssen wrote:
And- I want to update the default python that came om my macbook pro to 2.7.
Should I do install that from Python.org?
My advice? I've never had good luck trying to "update" the default
Python that comes with the Mac.
Bill -- I'm really curious what is
Tony> I do want 2.7 because it's a requirement at work. I want to have
Tony> the same versions & packages to avoid compatibility issues.
Tony> I can put Python2.7 in a different directory and leave 2.6 there
Tony> but I want the 2.7 installation to be the default one.
Default fo
I do want 2.7 because it's a requirement at work.
I want to have the same versions & packages to avoid compatibility issues.
I can put Python2.7 in a different directory and leave 2.6 there but I want
the 2.7 installation
to be the default one.
On Mon, Jan 17, 2011 at 9:17 AM, Bill Janssen wrote
Tony Cappellini wrote:
> And- I want to update the default python that came om my macbook pro to 2.7.
> Should I do install that from Python.org?
My advice? I've never had good luck trying to "update" the default
Python that comes with the Mac. I'd recommend just leaving it alone and
using it,
> And- I want to update the default python that came om my macbook pro to 2.7.
> Should I do install that from Python.org?
I personally think that this would be the simplest solution - but other
distributions do have their virtues and proponents. For example, Enthought
takes the pain out of mai
Hi Tony,
>1. Why are there so many "variations" of the Python installer for the Mac?
I think you'll find that the biggest difference between MacPorts python (and
fink python) and most other builds (python.org for example), is that MacPorts
uses X11 rather than Aqua (Apple's native window
In article
,
>1. Why are there so many "variations" of the Python installer for the
> Mac? (I'm not referring to 32-bit vs 64-bit architectures, although that
> does complicate things quite a bit).
>
> For example, there is the OSX installer at Python.org, then there are the
> Macports python
In article
,
Tony Cappellini wrote:
> On Sun, Jan 16, 2011 at 7:30 PM, Daniel O'Donovan
> wrote:
> > I think you'll find that the biggest difference between MacPorts python
> > (and fink python) and most other builds (python.org for example), is that
> > MacPorts uses X11 rather than Aqua (Appl
>>Using fink and MacPorts help integration with many linux type apps
> (particularly helpful for scientific programming) whilst the native,
> Framework builds are better >>for native looking Macintosh apps - and the
> Apple bundled python is obviously native.
>
> >>This is a simple summary, and the
Thanks Dan
Fink? Which one is that?
On Sun, Jan 16, 2011 at 7:30 PM, Daniel O'Donovan wrote:
> Hi Tony,
>
> >1. Why are there so many "variations" of the Python installer for the
> Mac?
>
>
> I think you'll find that the biggest difference between MacPorts python
> (and fink python) and mo
26 matches
Mail list logo
