Then, copied it to the CC\Data\Python directory and it works like a charm! I wrote a small compiler, and made a *.pyc out of the base64.py. So, I downloaded Python 2.6 installation and found that all modules were *.py and not *.pyc. I tried to copy a Python 2.7 base64.pyc and that gave me the "magic number" error - the versions were not compatible. You can add manually the *.pyc file to this directory, but it has to be Python 2.6 and not a higher version. If you encounter an "ImportError: no module named XYZ" that means that it's missing it in that directory. It's ImportError: no module named base64.Īny suggestions? Does Construct need to have these modules in a specific location? Or does it just hate base64? :P Any help would be greatly appreciated! Cheers!Įdit: SOLVED! For all those who will encounter this problem in the future: Construct Classic seems to come with some of the modules stored in \Data\Python but not all of them. Rest of the modules work pretty well, never had this error before. The problem is: I can't import base64 module! Nothing I try works, and Aptana Studio imports and uses base64 without any problem. it works OK in most cases, imported string, math, random, time modules without any problem.the "PYTHON ES" contains all classes and default functions, as well as import module lines.we're using a separate "PYTHON Event Sheet" that is imported at a start of every layout.I'll get into details right now (after this ad!): Until now it went smoothly enough, but suddenly, a little something came up. Me and my little indie game team are working on some projects, and we use CC as our primary app, mostly due to it's Python support, which really adds power and flexibility. Hi there! (ah, so I finally joined the forum, sorry to post a problem as my first post)
0 Comments
Leave a Reply. |