Pyserial for Python3 in OSX?

2014-02-15 Thread eglowstein . h
I need to do some serial I/O on a Mac running OSX Mavericks. I followed the 
instructions at

http://stackoverflow.com/questions/20082935/how-to-install-pip-for-python3-on-mac-os-x

to install pyserial. OSX already had Python 2.7 and pyserial seems to work okay 
in 2.7, but I can't figure out how to get to run in 3.3.3 or 3.3.4.

After I install pyserial, in python 2.7 I can get this:

Python 2.7.5 (default, Sep 12 2013, 21:33:34) 
[GCC 4.2.1 Compatible Apple LLVM 5.0 (clang-500.0.68)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> from serial.tools import list_ports
>>> list_ports.comports()
[['/dev/cu.Bluetooth-Incoming-Port', 'n/a', 'n/a'], ['/dev/cu.Bluetooth-Modem', 
'n/a', 'n/a'], ['/dev/cu.usbserial-AH012QEW', 'FT232R USB UART', 'USB 
VID:PID=403:6001 SNR=AH012QEW']]
>>> quit()

In Python 3, I get this:

Python 3.3.4 (default, Feb 15 2014, 21:28:44) 
[GCC 4.2.1 Compatible Apple LLVM 5.0 (clang-500.2.79)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> from serial.tools import list_ports
>>> list_ports.comports()
[]
>>> quit()


I see all sorts of messages around the web suggesting similar problems getting 
Python 3 on a Mac to talk to serial ports but I can't find any fixes. Is there 
a trick I haven't found yet? Many thanks in advance for a cure.

Howard
-- 
https://mail.python.org/mailman/listinfo/python-list


IDLE won't run after installing Python 3.3 in Windows

2014-02-18 Thread eglowstein . h
The next adventure in Python was to install Python 3 into a Windows XP machine. 
I had a previous 2.7 installation that I uninstalled and carefully removed all 
traces of from the directory and the registry.

I got the 'python-3.3.3.msi' from Python.org and installed it. From a command 
window I can run 'python' and I get the Python prompt. I have several Python 
programs on the machine. If I right click o one, I have the option of 'Edit in 
IDLE'. If I do that, the disk light blinks briefly, and then nothing. So I went 
into the \python33\lib\idlelib directory and from a CMD window, ran 'python 
idle.py'. That loads IDLE. but when I ask IDLE to load a file, it navigates to 
a FileOpen dialog and then closes everything when I actually open the file. I 
then tried the same thing but used 'pythonw' instead. Same deal.

I also saw some other threads here about how Python can get befuddled by 
firewalls, so I disabled that with no effect.

Any suggestions?  Thanks in advance!

Howard
-- 
https://mail.python.org/mailman/listinfo/python-list


Re: IDLE won't run after installing Python 3.3 in Windows

2014-02-19 Thread eglowstein . h
On Wednesday, February 19, 2014 2:00:52 PM UTC-5, Terry Reedy wrote:
> On 2/19/2014 12:50 PM, Mark Lawrence wrote:
> 
> > On 19/02/2014 17:30, Mark H. Harris wrote:
> 
> 
> 
> >> Does the previous version put stuff into the registry that keeps the
> 
> >> new version from running correctly?
> 
> 
> 
> > Not that I'm aware of.  But then again if people knew the answer it
> 
> > would have been posted by now.  Where is Terry Reedy when you need him?
> 
> 
> 
> Puzzled as to what the problem is.
> 
> 
> 
> -- 
> 
> Terry Jan Reedy


I was extremely careful to remove any last bit of evidence in the registry that 
*anything* in the c:\python27 and c:\python33 directories ever existed. After 
the registry was purged of everything and I deleted the directories, I 
restarted the machine to make sure the registry was read afresh (Windows XP is 
wacky that way) and then did a reinstall of Python 3.3.3. Before installing 
anything else, I launched a program by using the 'Edit in Idle' option. Idle 
comes up, flashes briefly and exits. The console window never appears. If I 
bring up a command window and go into the lib\idlelib directory and 
specifically start idle with "python idle.py" or "pythons idle.py", I get Idle, 
but no command window. Load a file in if launched with 'python', it appears but 
you can't run it. If you launch with 'pythons', the whole kit & caboodle just 
exits when you load the file.

That might not help, but that's all I saw. Is there someplace not obvious in 
the registry where any interesting information is kept?
-- 
https://mail.python.org/mailman/listinfo/python-list