<div dir="ltr"><div><div>William, are you the one that builds the WIndows versions of Scribus that are available for download?<br><br></div>My comment in the batch file is to alert the user to try and pick a release of Python that matches the release used to build the interpreter, e.g. the DLL, shipped with Scribus Windows 1.5. I want to avoid a scenario where someone links to their own version of Python that is incompatible with what has been tested and approved for use with Scribus.<br><br></div><br></div><div class="gmail_extra"><br><div class="gmail_quote">On Sat, May 30, 2015 at 9:30 AM, William Bader <span dir="ltr"><<a href="mailto:williambader@hotmail.com" target="_blank">williambader@hotmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><div dir="ltr"><br><br><div>> To: <a href="mailto:scribus-dev@lists.scribus.info" target="_blank">scribus-dev@lists.scribus.info</a><br>> From: <a href="mailto:jluc@no-log.org" target="_blank">jluc@no-log.org</a><br>> Date: Sat, 30 May 2015 18:05:45 +0200<br>> Subject: Re: [scribus-dev] Windows - Replacing Shipped Python Interpreter<span class=""><br>> <br>> Le 30/05/2015 17:05, John L. Poole a écrit :<br>> > uses Python installed on the<br>> > :: users system that matches the build of the Python interpreter<br>> > :: shipped with Scribus rather than the Python Interpreter shipped<br>> > :: with Scribus' build.<br>> <br>> <br>> > Before I go public with this on the Sribus Scripting wiki, I'd like to see<br>> > if there are any objections or problems with this approach.<br>> <br>> Is your comment wrong or my understanding ? What is the difference :<br>> - the Python interpreter shipped with Scribus<br>> - the Python Interpreter shipped with Scribus' build.<br>> <br>> ?<br>> <br>> JL<br></span></div><div><br></div><div>On my Linux laptop, "ldd /usr/local/bin/scribus | grep python" shows /lib64/libpython2.7.so.1.0</div><div><span style="font-size:12pt"><br></span></div><div><span style="font-size:12pt">"rpm -qa | grep python | grep devel" shows </span><span style="font-size:12pt">python-devel-2.7.5-16.fc20.x86_64</span></div><div><span style="font-size:12pt"><br></span></div><div><span style="font-size:12pt">"</span>rpm -qa | grep '^python-2'" shows <span style="font-size:12pt">python-2.7.5-16.fc20.x86_64</span></div><div><span style="font-size:12pt"><br></span></div><div><span style="font-size:12pt">So my Scribus executable was built against python 2.7.5, it dynamically links to </span>libpython2.7.so.1.0, and the python support files come from python-2.7.5.</div><div><br></div><div>Is the comment asking about the Windows equivalent of updating the libpython2.7.so.1.0 DLL or of updating the python-2.7.5-16.fc20.x86_64 package?</div><span class="HOEnZb"><font color="#888888"><div><br></div><div>William</div><div><br></div><div><br></div> </font></span></div></div>
<br>_______________________________________________<br>
scribus-dev mailing list<br>
<a href="mailto:scribus-dev@lists.scribus.net">scribus-dev@lists.scribus.net</a><br>
<a href="http://lists.scribus.net/mailman/listinfo/scribus-dev" target="_blank">http://lists.scribus.net/mailman/listinfo/scribus-dev</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature"><div dir="ltr">John L. Poole<br><br>P.O. Box 6566 <br>Napa, CA 94581-6566<br>707-812-1323<br><br><a href="mailto:jlpoole56@gmail.com" target="_blank">jlpoole56@gmail.com</a></div></div>
</div>