Yes, Python is installed to c:\python27.
Yes, Python is installed to c:\python27.
Do you have the PATH set Dan?
Yes, I checked the path through Windows, and c:\python27;c:\python\lib;c:\python27\scripts are all listed in the path statement.
C:\PYTHON27
C:\PYTHON27\LIB
installation and it didn't work. I also have the python27.dll file copied into the Mystic directory.
My Windows path only has C:\PYTHON27 on it as far as Python stuff goes, not sure if it matters as I never had any issues with MPS on Windows.
At the prompt if I...
echo %pythonhome%
C:\PYTHON27
echo %pythonpath%
C:\PYTHON27\LIB
c:\python27;c:\python\lib;c:\python27\scripts are all listed in the p statement.
My Windows path only has C:\PYTHON27 on it as far as Python stuff goes, not sure if it matters as I never had any issues with MPS on Windows.
echo %pythonhome%
C:\PYTHON27
echo %pythonpath%
C:\PYTHON27\LIB
Also, would you mind sharing the MPS? I've been trying to recreate the error here and had no luck.
And lastly as it's Windows, I have to ask... did you reboot?
installation and it didn't work. I also have the python27.dll file co into the Mystic directory.
Did you copy the dll? Or move the dll? You don't actually need to do anything with the dll and should leave it where it was installed.
I just deleted the one in the Mystic directory. It was a copy of the one that is located in the c:\windows\SysWOW64\python27.dll
I get this error while trying to run the demo that came with Mystic, testpython.mpy. I've tried a few different Mystic Python scripts and
they all give me issues.
I just deleted the one in the Mystic directory. It was a copy of the that is located in the c:\windows\SysWOW64\python27.dll
I'm sorry Dan, I'm at a complete loss. The only way I could recreate it was by messing with the dll file.
I'll sleep on it and see if anything else comes to mind.
I get this error while trying to run the demo that came with Mystic, testpython.mpy. I've tried a few different Mystic Python scripts and they all give me issues.
How do you call this within Mystic?
Hi All,
I have been fighting with trying to get Python to run through Mystic, and have not been able to do it. I have Python 2.7.13 installed and running
on my Win10 system. I can run Python scripts from a command prompt with
no problems.
When I try to run a Mystic Python script, I get the error stating that Mystic cannot find Python on the system. "Python not detected, press a key"
I'm not sure what I'm missing. Any assistance would be greatly appreciated.
On 03/20/17, Black Panther pondered and said...
Yes, Python is installed to c:\python27.
Do you have the PATH set Dan?
Hi All,
I have been fighting with trying to get Python to run through Mystic, and have not been able to do it. I have Python 2.7.13 installed and running
on my Win10 system. I can run Python scripts from a command prompt with
no problems.
When I try to run a Mystic Python script, I get the error stating that Mystic cannot find Python on the system. "Python not detected, press a key"
I have followed the information on the wiki.mysticbbs.com page.
PYTHONHOME is set to c:\python27
PYTHONPATH is set to c:\python27\lib
PATH is set for c:\python27;c:\python27\lib;c:\python17\scripts
Yes, Python is installed to c:\python27.
I run Windows 10 with Mystic and you need to edit your autoexec.bat
even though its in your windows enviornment variables.
I have been fighting with trying to get Python to run through Mystic, have not been able to do it. I have Python 2.7.13 installed and runni on my Win10 system. I can run Python scripts from a command prompt wi no problems.
There are a few things to keep in mind. Mystics' python is very
different than python. Mystic needs an Mystic Python script to be named with the MPY extension and it needs to be in the script directory. It
It is however possible to call a full, non-mystic python script as a
door, using the D3 or DD commands.
Now, this may be a dumb question, but I'm not finding an autoexec.bat on my system. It would still be in the root directory, correct? I looked in the root, and in the windows directories, but didn't see it.
Now, this may be a dumb question, but I'm not finding an autoexec.bat my system. It would still be in the root directory, correct? I looked the root, and in the windows directories, but didn't see it.
You cant see it because you have your system set to hide protected files in your file manager. unhide them and make hidden files to be also seen. after you get your autoexec.bat edited then you can go back and make them hidden again.
Are you running python-2.7.11 ? I am.
What python mods are you trying to run on Mystic?
Right now, I'd be happy if I could get the testpython.mpy to run. There are a few others that I have, but I'm waiting until I can get the testI would suggest that you approach Avon to see if you can arrange a remote session going for your Python gremlins. It has to be something were missing that we haven't thought of yet. Hes a great troubleshooter.
one to work before I try them.
Right now, I'd be happy if I could get the testpython.mpy to run. There are a few others that I have, but I'm waiting until I can get the test
one to work before I try them.
are a few others that I have, but I'm waiting until I can get the tes one to work before I try them.I would suggest that you approach Avon to see if you can arrange a remote session going for your Python gremlins. It has to be something were missing that we haven't thought of yet. Hes a great troubleshooter.
Right now, I'd be happy if I could get the testpython.mpy to run. The are a few others that I have, but I'm waiting until I can get the tes one to work before I try them.I would suggest that you approach Avon to see if you can arrange a remote session going for your Python gremlins. It has to be something were missing that we haven't thought of yet. Hes a great troubleshooter.
Right now, I'd be happy if I could get the testpython.mpy to run. The are a few others that I have, but I'm waiting until I can get the tes one to work before I try them.
I'm going to re-read all of these posts and see if I can understand
things further. By all accounts it should be working.
I'm going to re-read all of these posts and see if I can understand things further. By all accounts it should be working.That's why it's been frustrating me... I can't explain why it's not working, unless I'm missing something simple on this end... :)
We'll get to the bottom of this! It's now a puzzle that's got my need to solve engaged. :)
1) You're running Win10, 64-bit correct?
2) You installed 2.7.x Pthon, and it is ALSO 64-bit?
3) You're trying this on Mystic v1.12 A31, 64 bit?
We'll get to the bottom of this! It's now a puzzle that's got my need to solve engaged. :)
1) You're running Win10, 64-bit correct?Yes
2) You installed 2.7.x Pthon, and it is ALSO 64-bit?It didn't give an option to choose from the Python website. I chose 'Download' on the Python 2.7.13 version. I would think it would have detected it...
3) You're trying this on Mystic v1.12 A31, 64 bit?
Is there an easy way to tell which version I have? Otherwise, would overwriting the .exe files with the 64 bit versions work? I don't want to cause any further issues...
I appreciate your help. Thank you.
i asked you this a few threads back. did you see the link i gave you?
Is there an easy way to tell which version I have? Otherwise, would overwriting the .exe files with the 64 bit versions work? I don't want to cause any further issues...
3) You're trying this on Mystic v1.12 A31, 64 bit?
Is there an easy way to tell which version I have? Otherwise, would overwriting the .exe files with the 64 bit versions work? I don't wan cause any further issues...
There is not, well not that I know of. I do have this in a wish list so that mystic -ver will add this info to it's output.
This was the issue. I must have been running the 32 bit version of
Mystic. I just downloaded the 64 bit version and copied the .exe files over the top of what I had. Now it seems that it's working. Once you mentioned it, I couldn't remember which version I had installed of
Mystic.
Everything running 64 bit, and the Mystic Python works!! :)
Thank you Everyone for your help!
i asked you this a few threads back. did you see the link i gave you?Yes, and I did reply. I do have the PYTHONHOME and PYTHONPATH setting
set the same way they are in the image you provided. It's still not working.
3) You're trying this on Mystic v1.12 A31, 64 bit?This was the issue. I must have been running the 32 bit version of
Mystic. I just downloaded the 64 bit version and copied the .exe files Everything running 64 bit, and the Mystic Python works!! :)
On 03/23/17, Black Panther pondered and said...
Is there an easy way to tell which version I have? Otherwise, would
There is not, well not that I know of. I do have this in a wish list so that mystic -ver will add this info to it's output.
I've got everything unhidden. I can see the swapfile.sys, pagefile.sys, OS, BOOTNXT, etc. The only autoexec.bat file is the one that I created.
After re-booting it didn't make a difference... :(
But there's a "systems environment variable" settings control panel that let's you set all of this. If you can tell me what version of windows
you are running I can get the instructions on how to change it sent to you.
| Sysop: | sneaky |
|---|---|
| Location: | Ashburton,NZ |
| Users: | 3 |
| Nodes: | 8 (0 / 8) |
| Uptime: | 40:01:15 |
| Calls: | 2,137 |
| Calls today: | 2 |
| Files: | 11,149 |
| D/L today: |
10 files (9,977K bytes) |
| Messages: | 951,111 |