In article
,
Paul Wiseman wrote:
> On 1 December 2014 at 23:57, Ned Deily wrote:
>
> > [duplicate reply as the first seems to have disappeared]
> >
> > In article
> > ,
> > Paul Wiseman wrote:
> > > I don't think it's either of those. I think that hashlib.py must have
> > > changed in 2.7.9
On 1 December 2014 at 23:57, Ned Deily wrote:
> [duplicate reply as the first seems to have disappeared]
>
> In article
> ,
> Paul Wiseman 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_n
[duplicate reply as the first seems to have disappeared]
In article
,
Paul Wiseman 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 attribu
On 1 December 2014 at 17:08, John Lewis 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
On 1 December 2014 at 17:08, John Lewis 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 solv
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/
