On 14 September 2012 11:35, Ronald Oussoren wrote:
>
> On 14 Sep, 2012, at 12:26, Paul Wiseman wrote:
> >
> > Ah, yea I am indeed using the VERSIONER variable, I got myself confused
> because I was checking this,
> >
> > pauls-mac-pro:Python paul$ type python
> > python is hashed
> (/Library/Fra
On 14 Sep, 2012, at 12:26, Paul Wiseman wrote:
>
> Ah, yea I am indeed using the VERSIONER variable, I got myself confused
> because I was checking this,
>
> pauls-mac-pro:Python paul$ type python
> python is hashed
> (/Library/Frameworks/Python.framework/Versions/2.7/bin/python)
> paul$ file
On 14 September 2012 07:51, Ronald Oussoren wrote:
>
> On 13 Sep, 2012, at 23:41, Paul Wiseman wrote:
>
> On 13 September 2012 19:56, Michael McCracken > wrote:
>
>> Paul, it's like this:
>> setup(blah, options={"py2app": = {"bdist_base": "build/app1",
>> "dist_dir": "dist/app1"}})
>> setup(bla
On 13 Sep, 2012, at 23:41, Paul Wiseman wrote:
> On 13 September 2012 19:56, Michael McCracken
> wrote:
> Paul, it's like this:
> setup(blah, options={"py2app": = {"bdist_base": "build/app1",
> "dist_dir": "dist/app1"}})
> setup(blah, options={"py2app": = {"bdist_base": "build/app2",
> "dist_d
On Thu, Sep 13, 2012 at 4:13 PM, Paul Wiseman wrote:
> On 13 September 2012 20:16, Chris Barker wrote:
>>
>> On Thu, Sep 13, 2012 at 10:36 AM, Michael McCracken
>> wrote:
>> > FWIW, here's how I do something similar now, to avoid having many
>> > copies of the Qt libraries.
>>
>> cool! Thanks fo
On 13 September 2012 20:16, Chris Barker wrote:
> On Thu, Sep 13, 2012 at 10:36 AM, Michael McCracken
> wrote:
> > FWIW, here's how I do something similar now, to avoid having many
> > copies of the Qt libraries.
>
> cool! Thanks for the description
>
> > There is one master app, and several sub
On Thu, Sep 13, 2012 at 12:16 PM, Chris Barker wrote:
> On Thu, Sep 13, 2012 at 10:36 AM, Michael McCracken
> wrote:
>> FWIW, here's how I do something similar now, to avoid having many
>> copies of the Qt libraries.
>
> cool! Thanks for the description
>
>> There is one master app, and several s
On 13 September 2012 19:56, Michael McCracken
wrote:
> Paul, it's like this:
> setup(blah, options={"py2app": = {"bdist_base": "build/app1",
> "dist_dir": "dist/app1"}})
> setup(blah, options={"py2app": = {"bdist_base": "build/app2",
> "dist_dir": "dist/app2"}})
>
> For the full version, see my se
On Thu, Sep 13, 2012 at 10:36 AM, Michael McCracken
wrote:
> FWIW, here's how I do something similar now, to avoid having many
> copies of the Qt libraries.
cool! Thanks for the description
> There is one master app, and several sub-apps.
>
> * call setup() for each of the apps, generating full
Paul, it's like this:
setup(blah, options={"py2app": = {"bdist_base": "build/app1",
"dist_dir": "dist/app1"}})
setup(blah, options={"py2app": = {"bdist_base": "build/app2",
"dist_dir": "dist/app2"}})
For the full version, see my setup.py here: (ignore "windows-installer")
http://bazaar.launchpad.
On 13 September 2012 14:36, Ronald Oussoren wrote:
>
> On 13 Sep, 2012, at 15:17, Paul Wiseman wrote:
>
> On 13 September 2012 13:26, Ronald Oussoren wrote:
>
>>
>> On 13 Sep, 2012, at 14:17, Paul Wiseman wrote:
>>
>> On 13 September 2012 12:13, Ronald Oussoren wrote:
>>
>>>
>
I checke
On 13 September 2012 18:36, Michael McCracken
wrote:
> FWIW, here's how I do something similar now, to avoid having many
> copies of the Qt libraries.
> There is one master app, and several sub-apps.
>
> * call setup() for each of the apps, generating full separate apps
> with copies of the Qt lib
FWIW, here's how I do something similar now, to avoid having many
copies of the Qt libraries.
There is one master app, and several sub-apps.
* call setup() for each of the apps, generating full separate apps
with copies of the Qt libraries and other stuff
-- each call has a unique directory sent i
On Thu, Sep 13, 2012 at 1:53 AM, Ronald Oussoren wrote:
> Yea exactly, I have some smaller apps which are used for specific separate
> jobs (one has a simple gui and generates and gathers log files from the main
> app and zips them up should the main app ever fail to open for instance),
> the job
On 13 Sep, 2012, at 15:17, Paul Wiseman wrote:
> On 13 September 2012 13:26, Ronald Oussoren wrote:
>
> On 13 Sep, 2012, at 14:17, Paul Wiseman wrote:
>
>> On 13 September 2012 12:13, Ronald Oussoren wrote:
>>>
>>>
>>> I checked out the latest trunk
>>> (http://svn.pythonmac.org/py2app/p
On 13 September 2012 14:25, Paul Wiseman wrote:
> On 13 September 2012 14:17, Paul Wiseman wrote:
>
>> On 13 September 2012 13:26, Ronald Oussoren wrote:
>>
>>>
>>> On 13 Sep, 2012, at 14:17, Paul Wiseman wrote:
>>>
>>> On 13 September 2012 12:13, Ronald Oussoren wrote:
>>>
>>
> I
On 13 September 2012 14:17, Paul Wiseman wrote:
> On 13 September 2012 13:26, Ronald Oussoren wrote:
>
>>
>> On 13 Sep, 2012, at 14:17, Paul Wiseman wrote:
>>
>> On 13 September 2012 12:13, Ronald Oussoren wrote:
>>
>>>
>
I checked out the latest trunk (
http://svn.pythonmac.org/py
On 13 September 2012 13:26, Ronald Oussoren wrote:
>
> On 13 Sep, 2012, at 14:17, Paul Wiseman wrote:
>
> On 13 September 2012 12:13, Ronald Oussoren wrote:
>
>>
>>> I checked out the latest trunk (
>>> http://svn.pythonmac.org/py2app/py2app/trunk/), installed that and the
>>> problem has g
On 13 Sep, 2012, at 14:17, Paul Wiseman wrote:
> On 13 September 2012 12:13, Ronald Oussoren wrote:
>>
>>
>> I checked out the latest trunk
>> (http://svn.pythonmac.org/py2app/py2app/trunk/), installed that and the
>> problem has gone :)
>>
>> Not sure which version I had before, but I onl
On 13 September 2012 12:13, Ronald Oussoren wrote:
>
>>>
>> I checked out the latest trunk (
>> http://svn.pythonmac.org/py2app/py2app/trunk/), installed that and the
>> problem has gone :)
>>
>> Not sure which version I had before, but I only built this mac a week ago
>> or so, so think it's may
>
>
> I checked out the latest trunk
> (http://svn.pythonmac.org/py2app/py2app/trunk/), installed that and the
> problem has gone :)
>
> Not sure which version I had before, but I only built this mac a week ago or
> so, so think it's maybe the current version available for download
>
>
> Hm
On 13 September 2012 10:33, Paul Wiseman wrote:
> On 12 September 2012 19:27, Michael McCracken > wrote:
>
>> On Wed, Sep 12, 2012 at 10:54 AM, Paul Wiseman wrote:
>> > On 12 September 2012 18:13, Michael McCracken <
>> michael.mccrac...@gmail.com>
>> > wrote:
>> >>
>> >> On Wed, Sep 12, 2012 a
On 12 September 2012 19:27, Michael McCracken
wrote:
> On Wed, Sep 12, 2012 at 10:54 AM, Paul Wiseman wrote:
> > On 12 September 2012 18:13, Michael McCracken <
> michael.mccrac...@gmail.com>
> > wrote:
> >>
> >> On Wed, Sep 12, 2012 at 4:08 AM, Paul Wiseman
> wrote:
> >> > On 10 September 2012
On 13 Sep, 2012, at 10:47, Paul Wiseman wrote:
> On 13 September 2012 07:18, Ronald Oussoren wrote:
>
> On 10 Sep, 2012, at 16:37, Paul Wiseman wrote:
>
>> Ah,
>>
>> I've found out how to recreate the error
>>
>> If I create a main.py with nothing but 'import sqlalchemy'
>>
>> then use th
On 13 September 2012 07:18, Ronald Oussoren wrote:
>
> On 10 Sep, 2012, at 16:37, Paul Wiseman wrote:
>
> Ah,
>
> I've found out how to recreate the error
>
> If I create a main.py with nothing but 'import sqlalchemy'
>
> then use the following setup.py:
>
> from setuptools import setup
>
> setu
On Wed, Sep 12, 2012 at 10:54 AM, Paul Wiseman wrote:
> On 12 September 2012 18:13, Michael McCracken
> wrote:
>>
>> On Wed, Sep 12, 2012 at 4:08 AM, Paul Wiseman wrote:
>> > On 10 September 2012 13:18, Ronald Oussoren
>> > wrote:
>> >>
>> >>
>> >> On 9 Sep, 2012, at 20:34, Paul Wiseman wrote:
On 12 September 2012 18:13, Michael McCracken
wrote:
> On Wed, Sep 12, 2012 at 4:08 AM, Paul Wiseman wrote:
> > On 10 September 2012 13:18, Ronald Oussoren
> wrote:
> >>
> >>
> >> On 9 Sep, 2012, at 20:34, Paul Wiseman wrote:
> >>
> >> Hey,
> >>
> >> When building an app that is using sqlalchem
On Wed, Sep 12, 2012 at 4:08 AM, Paul Wiseman wrote:
> On 10 September 2012 13:18, Ronald Oussoren wrote:
>>
>>
>> On 9 Sep, 2012, at 20:34, Paul Wiseman wrote:
>>
>> Hey,
>>
>> When building an app that is using sqlalchemy I get this error:
>>
>> creating python loader for extension 'sqlalchemy
On 10 September 2012 13:18, Ronald Oussoren wrote:
>
> On 9 Sep, 2012, at 20:34, Paul Wiseman wrote:
>
> Hey,
>
> When building an app that is using sqlalchemy I get this error:
>
> creating python loader for extension 'sqlalchemy.cprocessors'
> error:
> /Users/paul/Source/Python/build/bdist.mac
On 9 Sep, 2012, at 20:34, Paul Wiseman wrote:
> Hey,
>
> When building an app that is using sqlalchemy I get this error:
>
> creating python loader for extension 'sqlalchemy.cprocessors'
> error:
> /Users/paul/Source/Python/build/bdist.macosx-10.6-intel/python2.7-standalone/app/temp/sqlalchem
Hey,
When building an app that is using sqlalchemy I get this error:
creating python loader for extension 'sqlalchemy.cprocessors'
error:
/Users/paul/Source/Python/build/bdist.macosx-10.6-intel/python2.7-standalone/app/temp/sqlalchemy/cprocessors.py:
No such file or directory
I took a look in si
31 matches
Mail list logo
