<html><body><div style="font-family: Arial; font-size: 10pt; color: #000000"><div>Thanks both - that's a bit clearer now.</div><div><br></div><div>I didn't get a patch, Ilya. Can you send me the link to your fork?</div><div><br></div><div><span name="x"></span>-- <br>Regards,<br><div><br></div>John Hackett<br>Icon Information Systems<br>74 Gibsons Hill, Norbury, London, SW16 3JS<br>t: 020 8764 2663<br>f: 020 8711 3370<br>m: 07801-231118<br>e: john.hackett@icon-is.co.uk<br>w: www.icon-is.co.uk<br>skype: john_hackett<br>twitter: @iconinfosys<span name="x"></span><br></div><div><br></div><hr id="zwchr"><blockquote style="border-left:2px solid #1010FF;margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;" data-mce-style="border-left: 2px solid #1010FF; margin-left: 5px; padding-left: 5px; color: #000; font-weight: normal; font-style: normal; text-decoration: none; font-family: Helvetica,Arial,sans-serif; font-size: 12pt;"><b>From: </b>pyqt-request@riverbankcomputing.com<br><b>To: </b>pyqt@riverbankcomputing.com<br><b>Sent: </b>Tuesday, 17 November, 2015 12:00:02 PM<br><b>Subject: </b>PyQt Digest, Vol 136, Issue 18<br><div><br></div>Send PyQt mailing list submissions to<br> pyqt@riverbankcomputing.com<br><div><br></div>To subscribe or unsubscribe via the World Wide Web, visit<br> https://www.riverbankcomputing.com/mailman/listinfo/pyqt<br>or, via email, send a message with subject or body 'help' to<br> pyqt-request@riverbankcomputing.com<br><div><br></div>You can reach the person managing the list at<br> pyqt-owner@riverbankcomputing.com<br><div><br></div>When replying, please edit your Subject line so it is more specific<br>than "Re: Contents of PyQt digest..."<br><div><br></div><br>Today's Topics:<br><div><br></div> 1. Re: pkg_resources error.... (lloyd konneker)<br> 2. Re: pkg_resources error.... (Ilya Kulakov)<br> 3. BUG pyrcc4 and pyrcc5 (Kuldeep Singh Dhaka)<br><div><br></div><br>----------------------------------------------------------------------<br><div><br></div>Message: 1<br>Date: Mon, 16 Nov 2015 10:20:56 -0500<br>From: lloyd konneker <bootch@nc.rr.com><br>To: pyqt@riverbankcomputing.com<br>Subject: Re: [PyQt] pkg_resources error....<br>Message-ID: <723DAA04-157B-412F-BD53-4DC589F61407@nc.rr.com><br>Content-Type: text/plain; charset=utf-8<br><div><br></div>You should probably wait for an answer from Ilya, but here is an educated guess:<br><div><br></div>pyqtdeploy implements a ‘loader’, that loads packages anytime an import statement is executed by the Python interpreter, from the special place/encoding that pyqtdeploy has bundled all the packages that your app uses.<br><div><br></div>You can search for ‘PEP302’ and within that document search for ‘get_data’. Basically it says that method is optional, and from what Ilya said, pyqtdeploy’s implementation of the loader API did not implement that optional method. You could look for that method definition in the source for pyqtdeploy’s implementation, since it is all open source.<br><div><br></div>I can’t speak to why in your particular circumstances the get_data method is needed.<br><div><br></div>Again, I could be wrong.<br><div><br></div>------------------------------<br><div><br></div>Message: 2<br>Date: Mon, 16 Nov 2015 13:22:20 -0500<br>From: Ilya Kulakov <kulakov.ilya@gmail.com><br>To: lloyd konneker <bootch@nc.rr.com><br>Cc: pyqt@riverbankcomputing.com<br>Subject: Re: [PyQt] pkg_resources error....<br>Message-ID: <B50DDEE1-45F0-41D2-972B-F1602722BE82@gmail.com><br>Content-Type: text/plain; charset=windows-1251<br><div><br></div>Indeed it is a missing optional method. Normally it should not lead to errors, but in reality since built in modules provide it, developers just relay on its presence. I'd try to update both pkg_resources and pytz first. If it won't help, it'd worth to study sources of pytz and, if the error is there, report to its developers.<br><div><br></div>Meanwhile, it should be possible to implement them for pyqtdeploy. I already implemented some of them in my fork. I believe I sent a patch, but if not, it should be easy to extract it from there.<br><div><br></div>Best Regards<br>Ilya Kulakov<br><div><br></div></blockquote></div></body></html>