Menu

#90 No module named serialwin32

closed-works-for-me
None
9
2014-02-17
2010-06-20
Carlos
No

pyserial does not work with windows XP and python 3.1. I have installed win32 extensions : pywin32-214.win32-py3.1.exe. The following error message occurs:
Traceback (most recent call last):
File "<pyshell#0>", line 1, in <module>
import serial
File "C:\Python31\lib\site-packages\serial\__init__.py", line 19, in <module>
from serialwin32 import *
ImportError: No module named serialwin32

I also notice other people are reporting the same issue with no solution available.

Discussion

  • Carlos

    Carlos - 2010-06-20
    • priority: 5 --> 9
     
  • Carlos

    Carlos - 2010-06-20

    I see this has been raised before, but I still don't see a solution.

     
  • Carlos

    Carlos - 2010-06-20
    • assigned_to: nobody --> cliechti
     
  • Peter Boström

    Peter Boström - 2010-07-12

    I saw this problem when installing rc2, which has no specifically labeled py3k (3.0) version. Installing pyserial-py3k-2.5-rc1.win32.exe got it working for me. Maybe try that out if you just want to get it working. (Using 3.1, Windows Vista)

     
  • Chris Liechti

    Chris Liechti - 2010-07-22
    • status: open --> pending-works-for-me
     
  • Chris Liechti

    Chris Liechti - 2010-07-22

    Please make sure you installed the -py3k version. Also, doing an "import serial" will not work if the current directory is in the root of an extracted source archive (it will pick up the local serial package which is not translated for python 3).

     
  • SourceForge Robot

    This Tracker item was closed automatically by the system. It was
    previously set to a Pending status, and the original submitter
    did not respond within 14 days (the time period specified by
    the administrator of this Tracker).

     
  • SourceForge Robot

    • status: pending-works-for-me --> closed-works-for-me
     

Log in to post a comment.

MongoDB Logo MongoDB