|
From: Bill S. <g4...@cl...> - 2015-04-28 23:07:40
|
On 28/04/2015 23:57, KI7MT wrote: > Hi Bill, Hi Greg, > > Yes, AsciiDoc works with Python2.5 through the latest Python2 which is > Python2.7.9 I believe. There won't be a Python2.8 from what I understand. > > However, AsciiDoc *will not* work with Python3.x., which is what WSPR > and WSJT use. Ah OK. So how do you deal with that on Linux? Do you have to do an alternate Python package switch every time you move between docs and WSPR/WSJT? > > > 73's > Greg, KI7MT 73 Bill G4WJS. > > > On 04/28/2015 03:28 PM, Bill Somerville wrote: >> On 28/04/2015 22:12, Bill Somerville wrote: >> >> <snip> >> >>> For Windows, adding Python27 is a sensitive situation with regards to >>> WSPR and WSJT builds. I will need to do some testing. Will take fare bit >>> of time to sort that all out. >>> Looking at the asciidoc prequisites it says Python 2.4 and up is OK so >>> it may not be an issue. I haven't put any Python checks in the WSJT-X >>> CMake script, it just finds asciidoc and takes the view that if you have >>> installed asciidoc then you really ought to have a working Python around. >> I've just tried asciidoc on Windows with Python 2.5 and it works fine. >> >> <snip> >> >> 73 >> Bill >> G4WJS. >> >> ------------------------------------------------------------------------------ >> One dashboard for servers and applications across Physical-Virtual-Cloud >> Widest out-of-the-box monitoring support with 50+ applications >> Performance metrics, stats and reports that give you Actionable Insights >> Deep dive visibility with transaction tracing using APM Insight. >> http://ad.doubleclick.net/ddm/clk/290420510;117567292;y >> _______________________________________________ >> wsjt-devel mailing list >> wsj...@li... >> https://lists.sourceforge.net/lists/listinfo/wsjt-devel >> |