Python loading woes once more!

I'm giving Python another shot with the latest MUSHclient, latest Python etc. And now I got an error different than the usual one, so it definitely is not the 'scripting engine is not registered' issue that causes trouble so often.



I bet it is a problem in Python, but I'd love to know.. what is this 'setting site' event? I got the sources for 4.43 and searched for that string, but no luck there. If it is a bug in Python I'd like to be able to point out what function call goes wrong when writing a bug report. :)

For what it matters, I am using english W7 Ultimate 64-bit, with Python 3.1.1 and the latest pywin32 for that same version.

(I don't have a compiler installed and I don't really want to go through the MUSHclient woes of getting it compiling either, so I hope Nick or someone else might be able to point out what bit goes wrong here... or if the fault is in MUSHclient, fix it in MUSH. =P)

Ok, nevermind. I seem to have found the relevant code by manually searching on ShowError instead. Weird. :/

Edit: searching subdirectories was turned off.. yeah, that'll cause such silly mistakes. :)

I'm getting the same thing. So, what was the problem?

I had Python 2.5 installed, scripting worked fine. I think I have 2.7 and 3.1 installed now, and suddenly scripting got broken.

Should I just upgrade my copy of MUSHclient? I wasn't planning on searching the source code since somebody else apparently had the problem.

Searched this site and found a discussion on python "installation:"
http://www.gammon.com.au/forum/?id=9844

Basically, it involves running this python file, which is part of the win32com package, registering the runtime as a COM object (a la axscript):
C:\Python27\Lib\site-packages\win32comext\axscript\client\pyscript.py --register

Change version/install location as necessary.

The ActiveScripting/WSH facility in the pywin32 package for Python is broken in the 3.0 branches. Install 2.6 and the pywin32 package for it, and to register it properly, just doubleclick the C:\Python2x\Lib\site-packages\win32comext\axscript\client\pyscript.py file.

I have already bugged the fact that the 3.x branch is bugged as hell for active scripting, but to my knowledge it isn't fixed yet.

Oh, and I am using 2.6 by the way. Not 2.7 because it was two days out or so when I installed, and there was no proper pywin32 package available for it yet at that time. :)

Edit: Just to clarify, this is a PYTHON issue, not a MUSHclient one. There's some annoying visual glitches when using MUSH @ W7, though. :(

I am having this problem too. I am using the latest version of Python and the windows package. I can't find anyone else having this problem except with MUSHclient. I am not trying to bash on MC - I love it and it's the only client I'll use but it sucks that I can't script in Python on it...

Hope someone figures out a fix soon.

I can't help but maybe a Python user will know.

I'd guess it's safe to say Python /does not/ work with MUSHclient for whatever reason any more. I have tried every single set of instructions to be found on the forum dealing with this subject from start to finish with fresh installs. I am relatively new to python and scripting in MUSHclient but not new to working with development environments so I am pretty confident that if it had anything to do with following the instructions incorrectly I would of stumbled on it by now. Guess scripting with Python is out. I don't usually give up on something but I have put more time into it at this point than utility I would of gained from being able to script in Python unfortunately.

Lua is better anyway. *shrug*

I'm sorry about that, but I don't have any control over what the Python developers release. The Lua interface however is supplied with the client, and should work reliably.