[scribus-dev] Windows - Replacing Shipped Python Interpreter

[William Bader]

Date: Sat, 30 May 2015 15:24:32 -0700
From: jlpoole56 at gmail.com
To: scribus-dev at lists.scribus.net
Subject: Re: [scribus-dev] Windows - Replacing Shipped Python Interpreter

William, are you the one that builds the WIndows versions of Scribus that are available for download?

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.



On Sat, May 30, 2015 at 9:30 AM, William Bader <williambader at hotmail.com> wrote:





> To: scribus-dev at lists.scribus.info
> From: jluc at no-log.org
> Date: Sat, 30 May 2015 18:05:45 +0200
> Subject: Re: [scribus-dev] Windows - Replacing Shipped Python Interpreter
> 
> Le 30/05/2015 17:05, John L. Poole a écrit :
> > uses Python installed on the
> >      :: users system that matches the build of the Python interpreter
> >      :: shipped with Scribus rather than the Python Interpreter shipped
> >      :: with Scribus' build.
> 
> 
>  > Before I go public with this on the Sribus Scripting wiki, I'd like to see
>  > if there are any objections or problems with this approach.
> 
> Is your comment wrong or my understanding ? What is the difference :
> - the Python interpreter shipped with Scribus
> - the Python Interpreter shipped with Scribus' build.
> 
> ?
> 
> JL

On my Linux laptop, "ldd /usr/local/bin/scribus | grep python" shows /lib64/libpython2.7.so.1.0
"rpm -qa | grep python | grep devel" shows python-devel-2.7.5-16.fc20.x86_64
"rpm -qa | grep '^python-2'" shows python-2.7.5-16.fc20.x86_64
So my Scribus executable was built against python 2.7.5, it dynamically links to libpython2.7.so.1.0, and the python support files come from python-2.7.5.
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?
William

 		 	   		  

_______________________________________________

scribus-dev mailing list

scribus-dev at lists.scribus.net

http://lists.scribus.net/mailman/listinfo/scribus-dev




-- 
John L. Poole

P.O. Box 6566 
Napa, CA 94581-6566
707-812-1323

jlpoole56 at gmail.com

John,
No, I do not do any Windows builds and I am not a Scribus developer.  I build Scribus on Linux for my own use.
I see your point that the download pages http://www.scribus.net/downloads-3/unstable-branch/ and http://www.scribus.net/downloads-3/stable-branch/ do not indicate where to get third party packages like python.  It is possible that everything is packaged in the download file.
If you have to maintain multiple versions of python, you could try virtualenv https://virtualenv.pypa.io/en/latest/
Regards,William



_______________________________________________
scribus-dev mailing list
scribus-dev at lists.scribus.net
http://lists.scribus.net/mailman/listinfo/scribus-dev 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.scribus.net/pipermail/scribus-dev/attachments/20150530/3925ef84/attachment-0001.html>