Subj : Re: Mystic Python on Linux
To   : Warpslide
From : The Godfather
Date : Mon Jun 29 2020 22:00:10

 Wa> Are you running Windows 10 32bit or 64bit?   I'm running 32bit and Python
 Wa> 2.7.18 works for me.  I found I had to check the "add Python to path"
 Wa> box when installing to get things running for me.
 Wa> 
 Wa> Jay

Jay,

I'm running 32bit 2.7.18 and Mystic 32bit to be sure they work well together.
The first time I installed 2.7.18, I was unaware of the "add Python to path"
box, so uninstalled and reinstalled it.  I think it was a crappy uninstall
that left traces of the prior install somewhere within windows, that
prevented a bunch of modules to install, as all path settings work just fine.
I'd ask, but haven't done the research myself yet, how to do a fully clean
uninstall of python (registery, etc..) prior to reinstallation.  I HAVE read
that it does solve a lot of issues.   Stizzed had a few issues initially, but
with time and attention to detail, managed to get a bunch of modules
installed on his 32bit machine and all works fine now.  So, it may also just
be the scripts themselves where provided instructions are leaving out unknown
needed modules that are required for it to work.  However the weak_ref error
is one frequently mentioned on Stackoverflow.com that I never seem to see a
resolution to and/or if I do they are for linux, not windows, and from all
I've read, not applicable.  Turbo C++ used to be "fun" to get up and running
back in the day ... but this one so far has been more complicated; then
again, I quit committing time to it due to other priorities.  Stizzed was
kind enough to send me his list of installed modules and versions to compare
when I have the time to sit down and see if thats the issue.  I do now it's
not environment variables.  My instructors for Java, who also teach Python,
checked those out for me and all were installed correctly.  

-tG

--- Mystic BBS v1.12 A45 2020/02/18 (Windows/32)
 * Origin: The Underground [@] theunderground.us:10023 <-port (21:1/165)

.