From cappy2112 at gmail.com  Sun Jan  5 04:44:17 2014
From: cappy2112 at gmail.com (Tony Cappellini)
Date: Sat, 4 Jan 2014 19:44:17 -0800
Subject: [Pythonmac-SIG] Bad installer for
	wxPython2.8-osx-ansi-2.8.12.1-universal-py2.7
Message-ID: <CABRXM4=ogqWV=vmt+GoBPZWMVgwEoVc8VcDTYVWOBBEwoVhajg@mail.gmail.com>

---------- Forwarded message ----------
From: Ned Deily <nad at acm.org>
To: pythonmac-sig at python.org
Cc:
Date: Sat, 28 Dec 2013 15:15:55 -0800
Subject: Re: [Pythonmac-SIG] Bad installer for
wxPython2.8-osx-ansi-2.8.12.1-universal-py2.7
In article <nad-86DEA0.13454428122013 at news.gmane.org>,
 Ned Deily <nad at acm.org> wrote:


>>sudo installer -pkg
>>/Volumes/wxPython2.9-osx-2.9.4.0-cocoa-py2.7/wxPython2.9-osx-cocoa-py2.7.
>>pkg -target /

Ok- thanks. This worked.
I was able to run the installer- without problems.

I do have one issue though. I am under the impression that
"universal-py2.7" means it will run under both 32 & 64 bit systems.

When I imported wx

import wx
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File
"/usr/local/lib/wxPython-ansi-2.8.12.1/lib/python2.7/site-packages/wx-2.8-mac-ansi/wx/__init__.py",
line 45, in <module>
    from wx._core import *
  File
"/usr/local/lib/wxPython-ansi-2.8.12.1/lib/python2.7/site-packages/wx-2.8-mac-ansi/wx/_core.py",
line 4, in <module>
    import _core_
ImportError:
/usr/local/lib/wxPython-ansi-2.8.12.1/lib/python2.7/site-packages/wx-2.8-mac-ansi/wx/_core_.so:
no appropriate 64-bit architecture (see "man python" for running in 32-bit
mode)

I am using the default version of Python (2.7.5) that comes with Mavericks
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pythonmac-sig/attachments/20140104/9a1a68d6/attachment.html>

From kw at codebykevin.com  Sun Jan  5 04:51:23 2014
From: kw at codebykevin.com (Kevin Walzer)
Date: Sat, 04 Jan 2014 22:51:23 -0500
Subject: [Pythonmac-SIG] Bad installer for
	wxPython2.8-osx-ansi-2.8.12.1-universal-py2.7
In-Reply-To: <CABRXM4=ogqWV=vmt+GoBPZWMVgwEoVc8VcDTYVWOBBEwoVhajg@mail.gmail.com>
References: <CABRXM4=ogqWV=vmt+GoBPZWMVgwEoVc8VcDTYVWOBBEwoVhajg@mail.gmail.com>
Message-ID: <52C8D6BB.2000203@codebykevin.com>

On 1/4/14, 10:44 PM, Tony Cappellini wrote:
>
> ---------- Forwarded message ----------
> From: Ned Deily <nad at acm.org <mailto:nad at acm.org>>
> To: pythonmac-sig at python.org <mailto:pythonmac-sig at python.org>
> Cc:
> Date: Sat, 28 Dec 2013 15:15:55 -0800
> Subject: Re: [Pythonmac-SIG] Bad installer for
> wxPython2.8-osx-ansi-2.8.12.1-universal-py2.7
> In article <nad-86DEA0.13454428122013 at news.gmane.org
> <mailto:nad-86DEA0.13454428122013 at news.gmane.org>>,
>   Ned Deily <nad at acm.org <mailto:nad at acm.org>> wrote:
>
>
>>>sudo installer -pkg
>>>/Volumes/wxPython2.9-osx-2.9.4.0-cocoa-py2.7/wxPython2.9-osx-cocoa-py2.7.
>>>pkg -target /
>
> Ok- thanks. This worked.
> I was able to run the installer- without problems.
>
> I do have one issue though. I am under the impression that
> "universal-py2.7" means it will run under both 32 & 64 bit systems.
>
> When I imported wx
>
> import wx
> Traceback (most recent call last):
>    File "<stdin>", line 1, in <module>
>    File
> "/usr/local/lib/wxPython-ansi-2.8.12.1/lib/python2.7/site-packages/wx-2.8-mac-ansi/wx/__init__.py",
> line 45, in <module>
>      from wx._core import *
>    File
> "/usr/local/lib/wxPython-ansi-2.8.12.1/lib/python2.7/site-packages/wx-2.8-mac-ansi/wx/_core.py",
> line 4, in <module>
>      import _core_
> ImportError:
> /usr/local/lib/wxPython-ansi-2.8.12.1/lib/python2.7/site-packages/wx-2.8-mac-ansi/wx/_core_.so:
> no appropriate 64-bit architecture (see "man python" for running in
> 32-bit mode)
>
> I am using the default version of Python (2.7.5) that comes with Mavericks
>

If you look at the version of wxPython referenced in the stack trace, 
it's 2.8, not the 2.9. one you installed. 2.8 is 32-bit only. Looks like 
Python is confused about which version to load. You may simply want to 
remove the 2.8 one altogether to avoid the conflict.

--Kevin

-- 
Kevin Walzer
Code by Kevin/Mobile Code by Kevin
http://www.codebykevin.com
http://www.wtmobilesoftware.com

From cappy2112 at gmail.com  Sun Jan  5 14:34:25 2014
From: cappy2112 at gmail.com (Tony Cappellini)
Date: Sun, 5 Jan 2014 05:34:25 -0800
Subject: [Pythonmac-SIG] Pythonmac-SIG Digest, Vol 129, Issue 1
In-Reply-To: <mailman.32.1388919602.16493.pythonmac-sig@python.org>
References: <mailman.32.1388919602.16493.pythonmac-sig@python.org>
Message-ID: <CABRXM4nXcr4dNOGyn3ySqs1M45WbM7vqhkvmTB3X5vmT1EXjCA@mail.gmail.com>

---------- Forwarded message ----------
From: Kevin Walzer <kw at codebykevin.com>
To: pythonmac-sig at python.org
Cc:
Date: Sat, 04 Jan 2014 22:51:23 -0500
Subject: Re: [Pythonmac-SIG] Bad installer for
wxPython2.8-osx-ansi-2.8.12.1-universal-py2.7
On 1/4/14, 10:44 PM, Tony Cappellini wrote:


>   Ned Deily <nad at acm.org <mailto:nad at acm.org>> wrote:
>
>
> sudo installer -pkg
>>> /Volumes/wxPython2.9-osx-2.9.4.0-cocoa-py2.7/wxPython2.9-
>>> osx-cocoa-py2.7.
>>> pkg -target /
>>>
>>
>
>
>>If you look at the version of wxPython referenced in the stack trace,
it's 2.8, not the 2.9. one you installed. 2.8 is 32-bit >>only. Looks like
Python is confused about which version to load. You may simply want to
remove the 2.8 one altogether >>to avoid the conflict.

If you look at my original post- I was referring to a wxPython 2.8
installer, that I have downloaded and suspected bad.
When Ned Deily replied, he referenced a 2.9 installer for some reason.

I have installed wx 2.8 using Ned's instructions (above), but substituting
the path and filename to the
installer in my original post.

Now- to get back to a clean slate- if I just delete the wxPython directory
that was installed, will that remove
everything needed to cleanup, or are there other steps involved in removing
a bad wx installation?

Thanks
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pythonmac-sig/attachments/20140105/38679a65/attachment.html>

From kw at codebykevin.com  Sun Jan  5 16:55:44 2014
From: kw at codebykevin.com (Kevin Walzer)
Date: Sun, 05 Jan 2014 10:55:44 -0500
Subject: [Pythonmac-SIG] Pythonmac-SIG Digest, Vol 129, Issue 1
In-Reply-To: <CABRXM4nXcr4dNOGyn3ySqs1M45WbM7vqhkvmTB3X5vmT1EXjCA@mail.gmail.com>
References: <mailman.32.1388919602.16493.pythonmac-sig@python.org>
 <CABRXM4nXcr4dNOGyn3ySqs1M45WbM7vqhkvmTB3X5vmT1EXjCA@mail.gmail.com>
Message-ID: <52C98080.1020806@codebykevin.com>

On 1/5/14, 8:34 AM, Tony Cappellini wrote:
> Now- to get back to a clean slate- if I just delete the
> wxPython directory that was installed, will that remove
> everything needed to cleanup, or are there other steps involved in
> removing a bad wx installation?

wxPython 3.0 has just been released. I'd download the one that supports 
Cocoa from http://wxpython.org/download.php#osx 
(wxPython3.0-osx-cocoa-py2.7). The disk image includes a script to 
remove previous installations of wxPython. Running this script and then 
installing 3.0 will accomplish two things: cleaning up your old 
installation; and supporting 64-bit Python. I bet you can run the 
installer package from the GUI, as well, since it's not an old package 
like wxPython 2.8.

Hope this helps,
Kevin

-- 
Kevin Walzer
Code by Kevin/Mobile Code by Kevin
http://www.codebykevin.com
http://www.wtmobilesoftware.com

From kw at codebykevin.com  Sun Jan  5 20:06:24 2014
From: kw at codebykevin.com (Kevin Walzer)
Date: Sun, 05 Jan 2014 14:06:24 -0500
Subject: [Pythonmac-SIG] Pythonmac-SIG Digest, Vol 129, Issue 1
In-Reply-To: <CABRXM4kB2hp50A6pZPwCTpgrcw4ANM+zU4x9i21xzD_Qi=BbAA@mail.gmail.com>
References: <mailman.32.1388919602.16493.pythonmac-sig@python.org>	<CABRXM4nXcr4dNOGyn3ySqs1M45WbM7vqhkvmTB3X5vmT1EXjCA@mail.gmail.com>	<52C98080.1020806@codebykevin.com>
 <CABRXM4kB2hp50A6pZPwCTpgrcw4ANM+zU4x9i21xzD_Qi=BbAA@mail.gmail.com>
Message-ID: <52C9AD30.8000004@codebykevin.com>

On 1/5/14, 1:13 PM, Tony Cappellini wrote:
> I'm going to install all my Python packages via macports- from now on. I
> haven't checked if wx 3.0 is supported there yet or not.
> I suspect not because it's too new. I also would like to stick with wx
> 2.x- to avoid API changes.
>
> Can I just delete the wx installation folder to cleanly remove that old
> wx installation, or is manual cleanup required?
>
> Thanks

I'd run the "remove" script from the download I pointed you to--it will 
clean everything up.

I'm sure you understand that using MacPorts for wx will require using 
their Python as well.

--Kevin
-- 
Kevin Walzer
Code by Kevin/Mobile Code by Kevin
http://www.codebykevin.com
http://www.wtmobilesoftware.com

From cappy2112 at gmail.com  Sun Jan  5 20:32:54 2014
From: cappy2112 at gmail.com (Tony Cappellini)
Date: Sun, 5 Jan 2014 11:32:54 -0800
Subject: [Pythonmac-SIG] Pythonmac-SIG Digest, Vol 129, Issue 1
In-Reply-To: <52C9AD30.8000004@codebykevin.com>
References: <mailman.32.1388919602.16493.pythonmac-sig@python.org>
 <CABRXM4nXcr4dNOGyn3ySqs1M45WbM7vqhkvmTB3X5vmT1EXjCA@mail.gmail.com>
 <52C98080.1020806@codebykevin.com>
 <CABRXM4kB2hp50A6pZPwCTpgrcw4ANM+zU4x9i21xzD_Qi=BbAA@mail.gmail.com>
 <52C9AD30.8000004@codebykevin.com>
Message-ID: <CABRXM4nL0=wQoxVZ8Ps9NBmp9NDMZ0e=O9me_jZGybzQoypzPg@mail.gmail.com>

> >>I'd run the "remove" script from the download I pointed you to--it will
> clean everything up.
> OK
>


> >>I'm sure you understand that using MacPorts for wx will require using
> their Python as well.

Yes- for what I'm doing, it shouldn't be a problem.
I want to leave the default Python installation on Mavericks as is, and use
a clean/separate environment via MacPorts & virtualenv

Thanks
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pythonmac-sig/attachments/20140105/1ab2ed81/attachment.html>

From brendan.simon at etrix.com.au  Fri Jan 31 01:53:53 2014
From: brendan.simon at etrix.com.au (Brendan Simon (eTRIX))
Date: Fri, 31 Jan 2014 11:53:53 +1100
Subject: [Pythonmac-SIG] Installing/updating development py2app
Message-ID: <52EAF421.70509@etrix.com.au>

Hi py2app devs,

A little while ago I  installed py2app from development branch to test
fixes on OS X 10.9.  I installed with "python setup.py develop",
including the other development modules that py2app complained about
(version compatibility).

My issue wasn't fixed, but looks like recent commits will fix the
issue.  I pulled the latest revision of py2app.  Do I need to do "python
setup.py develop" again ??  I did so, just to be sure.

The problem seems to have been fixed or improved, but now my application
crashes.  I'm not sure if I need to update the other modules (altgraph,
etc).  Do I need to do that?  Do I need to do "python setup.py develop"
everytime ?

What the best way, or recommend procedure, to try out new py2app commits ?

Thanks, Brendan.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pythonmac-sig/attachments/20140131/622178fc/attachment.html>