From poalman at gmail.com  Mon Dec  1 14:29:45 2014
From: poalman at gmail.com (Paul Wiseman)
Date: Mon, 1 Dec 2014 13:29:45 +0000
Subject: [Pythonmac-SIG] Installing python 2.7.9rc1 caused my frozen apps
	problems
Message-ID: <CACgdh2gxQwsVk59sdm4Jk6_U_v=iUyQo=C+m0CwwahsdqgJERg@mail.gmail.com>

I have a frozen app installed (built on a different machine using python
2.7.8 32/ppc)

I Installed python 2.7.9rc1 (32/pcc python.org installer) and I started
seeing errors from the built app on startup

the error occurred from import hashlib

  File
"/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/hashlib.py",
line 138, in <module>
    _hashlib.openssl_md_meth_names)
AttributeError: 'module' object has no attribute 'openssl_md_meth_names'

Installing 2.7.8 again on this machine, and the frozen app started working
again with no other changes.

Is this a problem with my setup or an issue with the freezing process?

Paul
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pythonmac-sig/attachments/20141201/95410cc8/attachment.html>

From poalman at gmail.com  Mon Dec  1 20:29:34 2014
From: poalman at gmail.com (Paul Wiseman)
Date: Mon, 1 Dec 2014 19:29:34 +0000
Subject: [Pythonmac-SIG] Installing python 2.7.9rc1 caused my frozen
	apps problems
In-Reply-To: <F2EA3943-2F23-4E33-A681-6D911C9508F9@deathstar.org>
References: <CACgdh2gxQwsVk59sdm4Jk6_U_v=iUyQo=C+m0CwwahsdqgJERg@mail.gmail.com>
 <F2EA3943-2F23-4E33-A681-6D911C9508F9@deathstar.org>
Message-ID: <CACgdh2iGfzDCk4B8BAp8c3TMURBVoencn2o-60hCh49iVPBfVQ@mail.gmail.com>

On 1 December 2014 at 17:08, John Lewis <jklewis at deathstar.org> wrote:

>
> Sounds like either the openssl module got corrupted or had a permission
> issue. It?s calling out a specific line number, if you wanted to track down
> the root problem you?d need to look there.
>
> In any case, a fresh install seems to have solved the problem.
>
>
Unless I'm mistaken- the frozen app should be completely unaffected and
independent from my local python install- it should be using it's own
internal hashlib, not the one from /Library/Frameworks folder.

The frozen app was working fine, I installed 2.7.9 and the frozen app
started throwing this error, then after reverting back to 2.7.8 the frozen
app was working again (I should stress that the frozen app was never
rebuilt and remained as-is)


> On Dec 1, 2014, at 7:29 AM, Paul Wiseman <poalman at gmail.com> wrote:
>
> I have a frozen app installed (built on a different machine using python
> 2.7.8 32/ppc)
>
> I Installed python 2.7.9rc1 (32/pcc python.org installer) and I started
> seeing errors from the built app on startup
>
> the error occurred from import hashlib
>
>   File
> "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/hashlib.py",
> line 138, in <module>
>     _hashlib.openssl_md_meth_names)
> AttributeError: 'module' object has no attribute 'openssl_md_meth_names'
>
> Installing 2.7.8 again on this machine, and the frozen app started working
> again with no other changes.
>
> Is this a problem with my setup or an issue with the freezing process?
>
> Paul
> _______________________________________________
> Pythonmac-SIG maillist  -  Pythonmac-SIG at python.org
> https://mail.python.org/mailman/listinfo/pythonmac-sig
> unsubscribe: https://mail.python.org/mailman/options/Pythonmac-SIG
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pythonmac-sig/attachments/20141201/7cfdec74/attachment.html>

From poalman at gmail.com  Mon Dec  1 20:35:20 2014
From: poalman at gmail.com (Paul Wiseman)
Date: Mon, 1 Dec 2014 19:35:20 +0000
Subject: [Pythonmac-SIG] Installing python 2.7.9rc1 caused my frozen
	apps problems
In-Reply-To: <F2EA3943-2F23-4E33-A681-6D911C9508F9@deathstar.org>
References: <CACgdh2gxQwsVk59sdm4Jk6_U_v=iUyQo=C+m0CwwahsdqgJERg@mail.gmail.com>
 <F2EA3943-2F23-4E33-A681-6D911C9508F9@deathstar.org>
Message-ID: <CACgdh2hOqFsDrfDpBLnheEPpoWquoqskF_bGdovGa7+z05EcVQ@mail.gmail.com>

On 1 December 2014 at 17:08, John Lewis <jklewis at deathstar.org> wrote:

>
> Sounds like either the openssl module got corrupted or had a permission
> issue. It?s calling out a specific line number, if you wanted to track down
> the root problem you?d need to look there.
>

I don't think it's either of those. I think that hashlib.py must have
changed in 2.7.9 from 2.7.8 (no longer has _hashlib.openssl_md_meth_names) so
the built app (running 2.7.8) expected that attribute to be there, but
somehow py2app or my usage of it is causing it to look in the system
libraries over the frozen libraries. Installing 2.7.8 again hides the issue
because whichever hashlib it uses would have the same behaviour because
they'll be identical (both from v2.7.8)


>
> In any case, a fresh install seems to have solved the problem.
>
> On Dec 1, 2014, at 7:29 AM, Paul Wiseman <poalman at gmail.com> wrote:
>
> I have a frozen app installed (built on a different machine using python
> 2.7.8 32/ppc)
>
> I Installed python 2.7.9rc1 (32/pcc python.org installer) and I started
> seeing errors from the built app on startup
>
> the error occurred from import hashlib
>
>   File
> "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/hashlib.py",
> line 138, in <module>
>     _hashlib.openssl_md_meth_names)
> AttributeError: 'module' object has no attribute 'openssl_md_meth_names'
>
> Installing 2.7.8 again on this machine, and the frozen app started working
> again with no other changes.
>
> Is this a problem with my setup or an issue with the freezing process?
>
> Paul
> _______________________________________________
> Pythonmac-SIG maillist  -  Pythonmac-SIG at python.org
> https://mail.python.org/mailman/listinfo/pythonmac-sig
> unsubscribe: https://mail.python.org/mailman/options/Pythonmac-SIG
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pythonmac-sig/attachments/20141201/a04a052f/attachment.html>

From nad at acm.org  Tue Dec  2 00:57:19 2014
From: nad at acm.org (Ned Deily)
Date: Mon, 01 Dec 2014 15:57:19 -0800
Subject: [Pythonmac-SIG] Installing python 2.7.9rc1 caused my frozen
	apps problems
References: <CACgdh2gxQwsVk59sdm4Jk6_U_v=iUyQo=C+m0CwwahsdqgJERg@mail.gmail.com>
 <F2EA3943-2F23-4E33-A681-6D911C9508F9@deathstar.org>
 <CACgdh2hOqFsDrfDpBLnheEPpoWquoqskF_bGdovGa7+z05EcVQ@mail.gmail.com>
Message-ID: <nad-5325FE.15571801122014@news.gmane.org>

[duplicate reply as the first seems to have disappeared]

In article 
<CACgdh2hOqFsDrfDpBLnheEPpoWquoqskF_bGdovGa7+z05EcVQ at mail.gmail.com>,
 Paul Wiseman <poalman at gmail.com> wrote:
> I don't think it's either of those. I think that hashlib.py must have
> changed in 2.7.9 from 2.7.8 (no longer has _hashlib.openssl_md_meth_names) so
> the built app (running 2.7.8) expected that attribute to be there, but
> somehow py2app or my usage of it is causing it to look in the system
> libraries over the frozen libraries. Installing 2.7.8 again hides the issue
> because whichever hashlib it uses would have the same behaviour because
> they'll be identical (both from v2.7.8)
> > In any case, a fresh install seems to have solved the problem.
> > On Dec 1, 2014, at 7:29 AM, Paul Wiseman <poalman at gmail.com> wrote:
> > I have a frozen app installed (built on a different machine using python
> > 2.7.8 32/ppc)
> >
> > I Installed python 2.7.9rc1 (32/pcc python.org installer) and I started
> > seeing errors from the built app on startup
> >
> > the error occurred from import hashlib
> >
> >   File
> > "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/hashlib.py"
> > ,
> > line 138, in <module>
> >     _hashlib.openssl_md_meth_names)
> > AttributeError: 'module' object has no attribute 'openssl_md_meth_names'
> >
> > Installing 2.7.8 again on this machine, and the frozen app started working
> > again with no other changes.
> >
> > Is this a problem with my setup or an issue with the freezing process?

The whole point of using py2app in normal, non-alias mode is to provide 
a self-contained, standalone app not dependent on any external 
Python-provided infrastructure, e.g. py files or extension modules or 
shared libs so something is wrong here.  The 'openssl_md_meth_names' was 
added to _hashlib.so for 2.7.9 (along with a lot of other changes to 
support the backport of upgraded ssl functionality from Python 3) so 
what appears to be happening here is that something in your app is 
incorrectly importing hashlib.py from the 2.7.9 installation in 
/Library/Frameworks along with (correctly) importing _hashlib.so from 
your py2app-produced app bundle.  I'm no expert on py2app but I did 
verify that a very simple app that used hashlib and was built with a 
current py2app and 2.7.8 did, in fact, work correctly when run in the 
presence of 2.7.9rc1.  So the question is what is going on with your 
app.  Questions that come to mind: (1) What is the full traceback (e.g. 
which file causes hashlib to be imported)?  (2) What is the value of 
sys.path at that point?  (3) What third-party modules are installed in 
the app and were any installed after using py2app?

-- 
 Ned Deily,
 nad at acm.org


From poalman at gmail.com  Tue Dec  2 01:02:32 2014
From: poalman at gmail.com (Paul Wiseman)
Date: Tue, 2 Dec 2014 00:02:32 +0000
Subject: [Pythonmac-SIG] Installing python 2.7.9rc1 caused my frozen
	apps problems
In-Reply-To: <nad-5325FE.15571801122014@news.gmane.org>
References: <CACgdh2gxQwsVk59sdm4Jk6_U_v=iUyQo=C+m0CwwahsdqgJERg@mail.gmail.com>
 <F2EA3943-2F23-4E33-A681-6D911C9508F9@deathstar.org>
 <CACgdh2hOqFsDrfDpBLnheEPpoWquoqskF_bGdovGa7+z05EcVQ@mail.gmail.com>
 <nad-5325FE.15571801122014@news.gmane.org>
Message-ID: <CACgdh2hH5CvyKbbca+xf3+Vkg_hvZBg8mQe7qAiti3UKXWVjHQ@mail.gmail.com>

On 1 December 2014 at 23:57, Ned Deily <nad at acm.org> wrote:

> [duplicate reply as the first seems to have disappeared]
>
> In article
> <CACgdh2hOqFsDrfDpBLnheEPpoWquoqskF_bGdovGa7+z05EcVQ at mail.gmail.com>,
>  Paul Wiseman <poalman at gmail.com> wrote:
> > I don't think it's either of those. I think that hashlib.py must have
> > changed in 2.7.9 from 2.7.8 (no longer has
> _hashlib.openssl_md_meth_names) so
> > the built app (running 2.7.8) expected that attribute to be there, but
> > somehow py2app or my usage of it is causing it to look in the system
> > libraries over the frozen libraries. Installing 2.7.8 again hides the
> issue
> > because whichever hashlib it uses would have the same behaviour because
> > they'll be identical (both from v2.7.8)
> > > In any case, a fresh install seems to have solved the problem.
> > > On Dec 1, 2014, at 7:29 AM, Paul Wiseman <poalman at gmail.com> wrote:
> > > I have a frozen app installed (built on a different machine using
> python
> > > 2.7.8 32/ppc)
> > >
> > > I Installed python 2.7.9rc1 (32/pcc python.org installer) and I
> started
> > > seeing errors from the built app on startup
> > >
> > > the error occurred from import hashlib
> > >
> > >   File
> > >
> "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/hashlib.py"
> > > ,
> > > line 138, in <module>
> > >     _hashlib.openssl_md_meth_names)
> > > AttributeError: 'module' object has no attribute
> 'openssl_md_meth_names'
> > >
> > > Installing 2.7.8 again on this machine, and the frozen app started
> working
> > > again with no other changes.
> > >
> > > Is this a problem with my setup or an issue with the freezing process?
>
> The whole point of using py2app in normal, non-alias mode is to provide
> a self-contained, standalone app not dependent on any external
> Python-provided infrastructure, e.g. py files or extension modules or
> shared libs so something is wrong here.  The 'openssl_md_meth_names' was
> added to _hashlib.so for 2.7.9 (along with a lot of other changes to
> support the backport of upgraded ssl functionality from Python 3) so
> what appears to be happening here is that something in your app is
> incorrectly importing hashlib.py from the 2.7.9 installation in
> /Library/Frameworks along with (correctly) importing _hashlib.so from
> your py2app-produced app bundle.


Yea I think you're right- I'm pretty sure that's what it must be


> I'm no expert on py2app but I did
> verify that a very simple app that used hashlib and was built with a
> current py2app and 2.7.8 did, in fact, work correctly when run in the
> presence of 2.7.9rc1.  So the question is what is going on with your
> app.  Questions that come to mind: (1) What is the full traceback (e.g.
> which file causes hashlib to be imported)?  (2) What is the value of
> sys.path at that point?  (3) What third-party modules are installed in
> the app and were any installed after using py2app?
>
>
This is the full traceback:

Traceback (most recent call last):
  File "/Applications/Utility.app/Contents/Resources/__boot__.py", line
316, in <module>
    _run()
  File "/Applications/Utility.app/Contents/Resources/__boot__.py", line
311, in _run
    exec(compile(source, path, 'exec'), globals(), globals())
  File "/Applications/Utility.app/Contents/Resources/context_main.py", line
3, in <module>
    from PythonApp.context.context import main
  File "PythonApp/context/context.pyc", line 3, in <module>  # from
PythonApp.redirectstd import redirect
  File "PythonApp/redirectstd.pyc", line 5, in <module>  # from PythonApp
import settings
  File "PythonApp/settings.pyc", line 7, in <module>  # import hashlib
  File
"/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/hashlib.py",
line 138, in <module>
    _hashlib.openssl_md_meth_names)
AttributeError: 'module' object has no attribute 'openssl_md_meth_names'
2014-12-01 23:44:57.204 Utility[72506:4648486] Utility Error

I printed out sys.path right before the import hashlib,
['/Library/Frameworks/Python.framework/Versions/2.7/lib/python27.zip',
'/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7',
'/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/plat-darwin',
'/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/plat-mac',
'/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/plat-mac/lib-scriptpackages',
'/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-tk',
'/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-old',
'/Applications/Utility.app/Contents/Resources/lib/python2.7/lib-dynload',
'/Applications/Utility.app/Contents/Resources/lib/python2.7/site-packages.zip',
'/Applications/Utility.app/Contents/Resources/lib/python2.7/site-packages']

There's no modifications in the code to sys.path or the pythonpath (I do
have modifications to PYTHONPATH in my .bash_profile- but those aren't
showing up in the sys.path output here, and I'm pretty sure that shouldn't
affect it right?)

There's quite a lot of 3rd party modules, non of which will have been
installed after the app was built. hashlib is imported pretty early, before
any 3rd party imports if that makes a difference.

I think I'll see tomorrow if I can't make a small sample app and setup.py
with py2app which I can reproduce the problem and I'll post it up on here.


> --
>  Ned Deily,
>  nad at acm.org
>
> _______________________________________________
> Pythonmac-SIG maillist  -  Pythonmac-SIG at python.org
> https://mail.python.org/mailman/listinfo/pythonmac-sig
> unsubscribe: https://mail.python.org/mailman/options/Pythonmac-SIG
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pythonmac-sig/attachments/20141202/4d5e8ea0/attachment.html>

From nad at acm.org  Tue Dec  2 01:17:51 2014
From: nad at acm.org (Ned Deily)
Date: Mon, 01 Dec 2014 16:17:51 -0800
Subject: [Pythonmac-SIG] Installing python 2.7.9rc1 caused my frozen
	apps problems
References: <CACgdh2gxQwsVk59sdm4Jk6_U_v=iUyQo=C+m0CwwahsdqgJERg@mail.gmail.com>
 <F2EA3943-2F23-4E33-A681-6D911C9508F9@deathstar.org>
 <CACgdh2hOqFsDrfDpBLnheEPpoWquoqskF_bGdovGa7+z05EcVQ@mail.gmail.com>
 <nad-5325FE.15571801122014@news.gmane.org>
 <CACgdh2hH5CvyKbbca+xf3+Vkg_hvZBg8mQe7qAiti3UKXWVjHQ@mail.gmail.com>
Message-ID: <nad-CF14D1.16175101122014@news.gmane.org>

In article 
<CACgdh2hH5CvyKbbca+xf3+Vkg_hvZBg8mQe7qAiti3UKXWVjHQ at mail.gmail.com>,
 Paul Wiseman <poalman at gmail.com> wrote:

> On 1 December 2014 at 23:57, Ned Deily <nad at acm.org> wrote:
> 
> > [duplicate reply as the first seems to have disappeared]
> >
> > In article
> > <CACgdh2hOqFsDrfDpBLnheEPpoWquoqskF_bGdovGa7+z05EcVQ at mail.gmail.com>,
> >  Paul Wiseman <poalman at gmail.com> wrote:
> > > I don't think it's either of those. I think that hashlib.py must have
> > > changed in 2.7.9 from 2.7.8 (no longer has
> > _hashlib.openssl_md_meth_names) so
> > > the built app (running 2.7.8) expected that attribute to be there, but
> > > somehow py2app or my usage of it is causing it to look in the system
> > > libraries over the frozen libraries. Installing 2.7.8 again hides the
> > issue
> > > because whichever hashlib it uses would have the same behaviour because
> > > they'll be identical (both from v2.7.8)
> > > > In any case, a fresh install seems to have solved the problem.
> > > > On Dec 1, 2014, at 7:29 AM, Paul Wiseman <poalman at gmail.com> wrote:
> > > > I have a frozen app installed (built on a different machine using
> > python
> > > > 2.7.8 32/ppc)
> > > >
> > > > I Installed python 2.7.9rc1 (32/pcc python.org installer) and I
> > started
> > > > seeing errors from the built app on startup
> > > >
> > > > the error occurred from import hashlib
> > > >
> > > >   File
> > > >
> > "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/hashlib.py"
> > > > ,
> > > > line 138, in <module>
> > > >     _hashlib.openssl_md_meth_names)
> > > > AttributeError: 'module' object has no attribute
> > 'openssl_md_meth_names'
> > > >
> > > > Installing 2.7.8 again on this machine, and the frozen app started
> > working
> > > > again with no other changes.
> > > >
> > > > Is this a problem with my setup or an issue with the freezing process?
> >
> > The whole point of using py2app in normal, non-alias mode is to provide
> > a self-contained, standalone app not dependent on any external
> > Python-provided infrastructure, e.g. py files or extension modules or
> > shared libs so something is wrong here.  The 'openssl_md_meth_names' was
> > added to _hashlib.so for 2.7.9 (along with a lot of other changes to
> > support the backport of upgraded ssl functionality from Python 3) so
> > what appears to be happening here is that something in your app is
> > incorrectly importing hashlib.py from the 2.7.9 installation in
> > /Library/Frameworks along with (correctly) importing _hashlib.so from
> > your py2app-produced app bundle.
> 
> 
> Yea I think you're right- I'm pretty sure that's what it must be
> 
> 
> > I'm no expert on py2app but I did
> > verify that a very simple app that used hashlib and was built with a
> > current py2app and 2.7.8 did, in fact, work correctly when run in the
> > presence of 2.7.9rc1.  So the question is what is going on with your
> > app.  Questions that come to mind: (1) What is the full traceback (e.g.
> > which file causes hashlib to be imported)?  (2) What is the value of
> > sys.path at that point?  (3) What third-party modules are installed in
> > the app and were any installed after using py2app?
> >
> >
> This is the full traceback:
> 
> Traceback (most recent call last):
>   File "/Applications/Utility.app/Contents/Resources/__boot__.py", line
> 316, in <module>
>     _run()
>   File "/Applications/Utility.app/Contents/Resources/__boot__.py", line
> 311, in _run
>     exec(compile(source, path, 'exec'), globals(), globals())
>   File "/Applications/Utility.app/Contents/Resources/context_main.py", line
> 3, in <module>
>     from PythonApp.context.context import main
>   File "PythonApp/context/context.pyc", line 3, in <module>  # from
> PythonApp.redirectstd import redirect
>   File "PythonApp/redirectstd.pyc", line 5, in <module>  # from PythonApp
> import settings
>   File "PythonApp/settings.pyc", line 7, in <module>  # import hashlib
>   File
> "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/hashlib.py",
> line 138, in <module>
>     _hashlib.openssl_md_meth_names)
> AttributeError: 'module' object has no attribute 'openssl_md_meth_names'
> 2014-12-01 23:44:57.204 Utility[72506:4648486] Utility Error
> 
> I printed out sys.path right before the import hashlib,
> ['/Library/Frameworks/Python.framework/Versions/2.7/lib/python27.zip',
> '/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7',
> '/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/plat-darwin',
> '/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/plat-mac',
> '/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/plat-mac/lib-
> scriptpackages',
> '/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-tk',
> '/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-old',
> '/Applications/Utility.app/Contents/Resources/lib/python2.7/lib-dynload',
> '/Applications/Utility.app/Contents/Resources/lib/python2.7/site-packages.zip'
> ,
> '/Applications/Utility.app/Contents/Resources/lib/python2.7/site-packages']
> 
> There's no modifications in the code to sys.path or the pythonpath (I do
> have modifications to PYTHONPATH in my .bash_profile- but those aren't
> showing up in the sys.path output here, and I'm pretty sure that shouldn't
> affect it right?)

That sys.path certainly looks wrong.  There shouldn't be any 
/Library/Frameworks paths when running in the app.  Yeah, your shell 
profile shouldn't enter into it when running a launched app.  You could 
also check the values for sys.executable, sys.prefix, and 
sys.exec_prefix.
 
> There's quite a lot of 3rd party modules, non of which will have been
> installed after the app was built. hashlib is imported pretty early, before
> any 3rd party imports if that makes a difference.
> 
> I think I'll see tomorrow if I can't make a small sample app and setup.py
> with py2app which I can reproduce the problem and I'll post it up on here.

Sounds like a good idea.  Of course, make sure you have the latest 
version of py2app and its dependencies, too.  Good luck!

-- 
 Ned Deily,
 nad at acm.org


From poalman at gmail.com  Tue Dec  2 19:29:57 2014
From: poalman at gmail.com (Paul Wiseman)
Date: Tue, 2 Dec 2014 18:29:57 +0000
Subject: [Pythonmac-SIG] Installing python 2.7.9rc1 caused my frozen
	apps problems
In-Reply-To: <nad-CF14D1.16175101122014@news.gmane.org>
References: <CACgdh2gxQwsVk59sdm4Jk6_U_v=iUyQo=C+m0CwwahsdqgJERg@mail.gmail.com>
 <F2EA3943-2F23-4E33-A681-6D911C9508F9@deathstar.org>
 <CACgdh2hOqFsDrfDpBLnheEPpoWquoqskF_bGdovGa7+z05EcVQ@mail.gmail.com>
 <nad-5325FE.15571801122014@news.gmane.org>
 <CACgdh2hH5CvyKbbca+xf3+Vkg_hvZBg8mQe7qAiti3UKXWVjHQ@mail.gmail.com>
 <nad-CF14D1.16175101122014@news.gmane.org>
Message-ID: <CACgdh2j2s7oTuPxXHVC_K8KWPfjAseiQtTM1G8=uXHha_6MQLg@mail.gmail.com>

On 2 December 2014 at 00:17, Ned Deily <nad at acm.org> wrote:

> In article
> <CACgdh2hH5CvyKbbca+xf3+Vkg_hvZBg8mQe7qAiti3UKXWVjHQ at mail.gmail.com>,
>  Paul Wiseman <poalman at gmail.com> wrote:
>
> > On 1 December 2014 at 23:57, Ned Deily <nad at acm.org> wrote:
> >
> > > [duplicate reply as the first seems to have disappeared]
> > >
> > > In article
> > > <CACgdh2hOqFsDrfDpBLnheEPpoWquoqskF_bGdovGa7+z05EcVQ at mail.gmail.com>,
> > >  Paul Wiseman <poalman at gmail.com> wrote:
> > > > I don't think it's either of those. I think that hashlib.py must have
> > > > changed in 2.7.9 from 2.7.8 (no longer has
> > > _hashlib.openssl_md_meth_names) so
> > > > the built app (running 2.7.8) expected that attribute to be there,
> but
> > > > somehow py2app or my usage of it is causing it to look in the system
> > > > libraries over the frozen libraries. Installing 2.7.8 again hides the
> > > issue
> > > > because whichever hashlib it uses would have the same behaviour
> because
> > > > they'll be identical (both from v2.7.8)
> > > > > In any case, a fresh install seems to have solved the problem.
> > > > > On Dec 1, 2014, at 7:29 AM, Paul Wiseman <poalman at gmail.com>
> wrote:
> > > > > I have a frozen app installed (built on a different machine using
> > > python
> > > > > 2.7.8 32/ppc)
> > > > >
> > > > > I Installed python 2.7.9rc1 (32/pcc python.org installer) and I
> > > started
> > > > > seeing errors from the built app on startup
> > > > >
> > > > > the error occurred from import hashlib
> > > > >
> > > > >   File
> > > > >
> > >
> "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/hashlib.py"
> > > > > ,
> > > > > line 138, in <module>
> > > > >     _hashlib.openssl_md_meth_names)
> > > > > AttributeError: 'module' object has no attribute
> > > 'openssl_md_meth_names'
> > > > >
> > > > > Installing 2.7.8 again on this machine, and the frozen app started
> > > working
> > > > > again with no other changes.
> > > > >
> > > > > Is this a problem with my setup or an issue with the freezing
> process?
> > >
> > > The whole point of using py2app in normal, non-alias mode is to provide
> > > a self-contained, standalone app not dependent on any external
> > > Python-provided infrastructure, e.g. py files or extension modules or
> > > shared libs so something is wrong here.  The 'openssl_md_meth_names'
> was
> > > added to _hashlib.so for 2.7.9 (along with a lot of other changes to
> > > support the backport of upgraded ssl functionality from Python 3) so
> > > what appears to be happening here is that something in your app is
> > > incorrectly importing hashlib.py from the 2.7.9 installation in
> > > /Library/Frameworks along with (correctly) importing _hashlib.so from
> > > your py2app-produced app bundle.
> >
> >
> > Yea I think you're right- I'm pretty sure that's what it must be
> >
> >
> > > I'm no expert on py2app but I did
> > > verify that a very simple app that used hashlib and was built with a
> > > current py2app and 2.7.8 did, in fact, work correctly when run in the
> > > presence of 2.7.9rc1.  So the question is what is going on with your
> > > app.  Questions that come to mind: (1) What is the full traceback (e.g.
> > > which file causes hashlib to be imported)?  (2) What is the value of
> > > sys.path at that point?  (3) What third-party modules are installed in
> > > the app and were any installed after using py2app?
> > >
> > >
> > This is the full traceback:
> >
> > Traceback (most recent call last):
> >   File "/Applications/Utility.app/Contents/Resources/__boot__.py", line
> > 316, in <module>
> >     _run()
> >   File "/Applications/Utility.app/Contents/Resources/__boot__.py", line
> > 311, in _run
> >     exec(compile(source, path, 'exec'), globals(), globals())
> >   File "/Applications/Utility.app/Contents/Resources/context_main.py",
> line
> > 3, in <module>
> >     from PythonApp.context.context import main
> >   File "PythonApp/context/context.pyc", line 3, in <module>  # from
> > PythonApp.redirectstd import redirect
> >   File "PythonApp/redirectstd.pyc", line 5, in <module>  # from PythonApp
> > import settings
> >   File "PythonApp/settings.pyc", line 7, in <module>  # import hashlib
> >   File
> >
> "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/hashlib.py",
> > line 138, in <module>
> >     _hashlib.openssl_md_meth_names)
> > AttributeError: 'module' object has no attribute 'openssl_md_meth_names'
> > 2014-12-01 23:44:57.204 Utility[72506:4648486] Utility Error
> >
> > I printed out sys.path right before the import hashlib,
> > ['/Library/Frameworks/Python.framework/Versions/2.7/lib/python27.zip',
> > '/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7',
> >
> '/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/plat-darwin',
> >
> '/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/plat-mac',
> >
> '/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/plat-mac/lib-
> > scriptpackages',
> > '/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-tk',
> >
> '/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-old',
> > '/Applications/Utility.app/Contents/Resources/lib/python2.7/lib-dynload',
> >
> '/Applications/Utility.app/Contents/Resources/lib/python2.7/site-packages.zip'
> > ,
> >
> '/Applications/Utility.app/Contents/Resources/lib/python2.7/site-packages']
> >
> > There's no modifications in the code to sys.path or the pythonpath (I do
> > have modifications to PYTHONPATH in my .bash_profile- but those aren't
> > showing up in the sys.path output here, and I'm pretty sure that
> shouldn't
> > affect it right?)
>
> That sys.path certainly looks wrong.  There shouldn't be any
> /Library/Frameworks paths when running in the app.  Yeah, your shell
> profile shouldn't enter into it when running a launched app.  You could
> also check the values for sys.executable, sys.prefix, and
> sys.exec_prefix.
>
>
I tracked down the issue! Someone (possibly me) had put the
line sys.path.insert(0,os.path.abspath(os.path.curdir)) at the top of the
build script - I didn't think to search that when looking for sys.path
modifications.

I'm not sure what the purpose of that line was, but removing it solves the
issue and doesn't appear to have broken anything.

Thanks for your help!! :)


> > There's quite a lot of 3rd party modules, non of which will have been
> > installed after the app was built. hashlib is imported pretty early,
> before
> > any 3rd party imports if that makes a difference.
> >
> > I think I'll see tomorrow if I can't make a small sample app and setup.py
> > with py2app which I can reproduce the problem and I'll post it up on
> here.
>
> Sounds like a good idea.  Of course, make sure you have the latest
> version of py2app and its dependencies, too.  Good luck!
>
> --
>  Ned Deily,
>  nad at acm.org
>
> _______________________________________________
> Pythonmac-SIG maillist  -  Pythonmac-SIG at python.org
> https://mail.python.org/mailman/listinfo/pythonmac-sig
> unsubscribe: https://mail.python.org/mailman/options/Pythonmac-SIG
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pythonmac-sig/attachments/20141202/3ff17c30/attachment.html>

From michaeldforzano at gmail.com  Fri Dec 12 07:20:58 2014
From: michaeldforzano at gmail.com (Michael Forzano)
Date: Thu, 11 Dec 2014 22:20:58 -0800
Subject: [Pythonmac-SIG] Issue Building App with Py2app 0.9
Message-ID: <CAKRnMMVRmiTos+dJBA5MCue57r7m5aGWkajs7oHW8i5cchubfg@mail.gmail.com>

Hello,

I am attempting to build my app on OSX 10.8, the stock Python 2.7.2
and the latest Py2app (0.9 I believe). I am getting the error
TypeError: dyld_find() got an unexpected keyword argument 'loader' as
described in https://bitbucket.org/ronaldoussoren/py2app/issue/137/py2app-problems-using-enthought-python.
I made the change to the file in question changing loader to
loader_path. The app builds successfully, but  when I attempt to run
it I get "ImportError: No Module name os".

If there is no plan to fix this soon, could someone let me know which
versions of these packages are known to work? It would be much
appreciated as this is blocking our upcoming release.

Thanks,
Mike

From michaeldforzano at gmail.com  Sat Dec 13 04:02:33 2014
From: michaeldforzano at gmail.com (Michael Forzano)
Date: Fri, 12 Dec 2014 19:02:33 -0800
Subject: [Pythonmac-SIG] Issue Building App with Py2app 0.9
In-Reply-To: <CAKRnMMVRmiTos+dJBA5MCue57r7m5aGWkajs7oHW8i5cchubfg@mail.gmail.com>
References: <CAKRnMMVRmiTos+dJBA5MCue57r7m5aGWkajs7oHW8i5cchubfg@mail.gmail.com>
Message-ID: <CAKRnMMVxkbCB1TpUrG3CqX5XV9fS2XaNxQjv5mn0t_dK4NHp-w@mail.gmail.com>

I am now using Py2App 0.7 and getting further than I was. However,
now, I am unable t get Py2App to include the faulthandler package
which is required by one of my dependencies. Even if I explicitly
specify it with the -i option (-i faulthandler), I still get
ImportError: No module named faulthandler. How can I get Py2App to
include this package? Any help would be much appreciated!

On 12/11/14, Michael Forzano <michaeldforzano at gmail.com> wrote:
> Hello,
>
> I am attempting to build my app on OSX 10.8, the stock Python 2.7.2
> and the latest Py2app (0.9 I believe). I am getting the error
> TypeError: dyld_find() got an unexpected keyword argument 'loader' as
> described in
> https://bitbucket.org/ronaldoussoren/py2app/issue/137/py2app-problems-using-enthought-python.
> I made the change to the file in question changing loader to
> loader_path. The app builds successfully, but  when I attempt to run
> it I get "ImportError: No Module name os".
>
> If there is no plan to fix this soon, could someone let me know which
> versions of these packages are known to work? It would be much
> appreciated as this is blocking our upcoming release.
>
> Thanks,
> Mike
>