[issue15982] asyncore.dispatcher does not handle windows socket error code correctly (namely WSAEWOULDBLOCK 10035)

Change by Irit Katriel : -- resolution: -> wont fix stage: -> resolved status: open -> closed superseder: asyncore.dispatcher.recv doesn't handle EAGAIN / EWOULDBLOCK -> Close asyncore/asynchat/smtpd issues and list them here ___ Python tracker

[issue32729] socket error handling needed

Change by Serhiy Storchaka : -- type: crash -> behavior ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue32729] socket error handling needed

yang added the comment: Oh.. you are right. I think it's my bug. here is code ``` import urllib3 import certifi from functools import wraps import signal from urllib3 import Timeout def timeoutdec(sec): def decorator(func): def _timeout(signum, frame):

[issue32729] socket error handling needed

INADA Naoki added the comment: And your screenshot doesn't contain "full" traceback chain. It can be very important hint about who creates invalid TimeoutError. -- ___ Python tracker

[issue32729] socket error handling needed

INADA Naoki added the comment: It may be bug of raising TimeoutError, not catching. That's why I want example code to reproduce. -- ___ Python tracker

[issue32729] socket error handling needed

yang added the comment: When timeout error occurred in urllib3.Poolmanager.urlopen(), the built-in TimeoutError raised which is not caught in existing timeout exception clause. Thus, It is caught by 'error' except and it is not checking Nonetype so that raising IndexError

[issue32729] socket error handling needed

INADA Naoki added the comment: Please give us reproducible example. Otherwise, we can't know it's our bug or it's bug of caller. -- nosy: +inada.naoki ___ Python tracker

[issue32729] socket error handling needed

yang added the comment: In the lib/socket.py Inside of readinto function, 576 line needed None type check or something -- ___ Python tracker

[issue32729] socket error handling needed

Change by yang : -- keywords: +patch pull_requests: +5286 stage: -> patch review ___ Python tracker ___

[issue32729] socket error handling needed

yang <rkd...@naver.com> added the comment: If socket error occurred I think it is a timeout error or something. but It's not error raising correctly but IndexError which is not correct error MSG. It will be fixed or None type check needed. -- resolution: -&

[issue32729] socket error handling needed

New submission from 양영일 <sun020...@gmail.com>: socket error handling needed -- components: IO messages: 311313 nosy: 양영일 priority: normal severity: normal status: open title: socket error handling needed type: crash versions: Python 3.4, Python 3.5, Python 3.6, Python 3.7, Pyth

[issue15982] asyncore.dispatcher does not handle windows socket error code correctly (namely WSAEWOULDBLOCK 10035)

STINNER Victor added the comment: I reopen the issue since David Vitek proposed a patch. -- resolution: duplicate -> status: closed -> open ___ Python tracker

[issue15982] asyncore.dispatcher does not handle windows socket error code correctly (namely WSAEWOULDBLOCK 10035)

David Vitek added the comment: It doesn't look like the fix for issue #16133 fixed this problem, or perhaps it only fixed it for asynchat but not asyncore. I have attached a patch (against python 2, since this is where I needed it fixed). The patch treats WSA flavors

Re: SSL Socket Error

shdwkee...@gmail.com wrote: Ive setup a Debian server with Python 2.7.9. Have everything running and SSL as well, but when I try and login to using HTTPS:// I get this error: Incoming web connection from ('192.168.15.177', 53202) error: uncaptured python exception, closing channel

SSL Socket Error

Ive setup a Debian server with Python 2.7.9. Have everything running and SSL as well, but when I try and login to using HTTPS:// I get this error: Incoming web connection from ('192.168.15.177', 53202) error: uncaptured python exception, closing channel main.AlarmServer listening :8111 at

[issue15982] asyncore.dispatcher does not handle windows socket error code correctly (namely WSAEWOULDBLOCK 10035)

Changes by STINNER Victor victor.stin...@gmail.com: -- resolution: - duplicate status: open - closed superseder: - asyncore.dispatcher.recv doesn't handle EAGAIN / EWOULDBLOCK ___ Python tracker rep...@bugs.python.org

[issue15982] asyncore.dispatcher does not handle windows socket error code correctly (namely WSAEWOULDBLOCK 10035)

STINNER Victor added the comment: This issue looks like a duplicate of the issue #16133. -- nosy: +haypo ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15982 ___

[issue16646] FTP.makeport() loses socket error details

Giampaolo Rodola' added the comment: Why did you replace socket.error with OSError? I think we should use socket.create_connection() as a guide line: http://hg.python.org/cpython/file/45dfb657b430/Lib/socket.py#l401 A patch is in attachment. -- Added file:

[issue16646] FTP.makeport() loses socket error details

Changes by Giampaolo Rodola' g.rod...@gmail.com: -- assignee: - giampaolo.rodola ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16646 ___ ___

[issue16646] FTP.makeport() loses socket error details

Serhiy Storchaka added the comment: socket.error is alias to OSError since 3.3 (PEP 3151). For versions 3.3 socket.error should be preserved. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16646

[issue16646] FTP.makeport() loses socket error details

Serhiy Storchaka added the comment: I agree that copying a code from socket.create_connection() is a good idea. Modernizing socket.error to OSError can be done in a separated issue. -- stage: patch review - commit review ___ Python tracker

[issue16646] FTP.makeport() loses socket error details

Roundup Robot added the comment: New changeset b7419f88c628 by Giampaolo Rodola' in branch '3.2': Fix issue #16646: ftplib.FTP.makeport() might lose socket error details. (patch by Serhiy Storchaka) http://hg.python.org/cpython/rev/b7419f88c628 New changeset b8289a08d720 by Giampaolo Rodola

[issue16646] FTP.makeport() loses socket error details

Roundup Robot added the comment: New changeset 6e07be3dfb6b by Giampaolo Rodola' in branch '2.7': Fix issue #16646: ftplib.FTP.makeport() might lose socket error details. (patch by Serhiy Storchaka) http://hg.python.org/cpython/rev/6e07be3dfb6b

[issue16646] FTP.makeport() loses socket error details

Changes by Giampaolo Rodola' g.rod...@gmail.com: -- resolution: - fixed stage: commit review - committed/rejected status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16646

[issue16647] LMTP.connect() loses socket error details

Roundup Robot added the comment: New changeset 1a2ead9faa3f by Andrew Svetlov in branch '3.2': Issue #16647: save socket error details in LMTP.connect() http://hg.python.org/cpython/rev/1a2ead9faa3f New changeset 6d805653843a by Andrew Svetlov in branch '3.3': Issue #16647: save socket error

[issue16647] LMTP.connect() loses socket error details

Andrew Svetlov added the comment: Fixed. Thanks, Serhiy. -- nosy: +asvetlov resolution: - fixed stage: patch review - committed/rejected status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16647

[issue16646] FTP.makeport() loses socket error details

Serhiy Storchaka added the comment: I doubt about the committed variant of patch. Note that both my original patch and socket.create_connection() use intermediate variable for catching an exception. This is done deliberately. Example: err = None try: raise ValueError ... except ValueError

[issue16646] FTP.makeport() loses socket error details

Roundup Robot added the comment: New changeset dcefa2c8386b by Giampaolo Rodola' in branch '3.2': Issue 16646 (ftplib): deliberately use intermediate variable after catching exception http://hg.python.org/cpython/rev/dcefa2c8386b New changeset da161499d0c0 by Giampaolo Rodola' in branch '3.3':

[issue16646] FTP.makeport() loses socket error details

Giampaolo Rodola' added the comment: Ouch! My bad. Thanks. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16646 ___ ___ Python-bugs-list mailing

[issue16646] FTP.makeport() loses socket error details

Changes by Antoine Pitrou pit...@free.fr: -- nosy: +giampaolo.rodola ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16646 ___ ___ Python-bugs-list

[issue16647] LMTP.connect() loses socket error details

Changes by Jesús Cea Avión j...@jcea.es: -- nosy: +jcea ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16647 ___ ___ Python-bugs-list mailing list

[issue16647] LMTP.connect() loses socket error details

Serhiy Storchaka added the comment: Patch updated. It can be simpler. -- Added file: http://bugs.python.org/file28269/smtplib_LMTP_connect_raise_err_2.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16647

[issue16647] LMTP.connect() loses socket error details

Changes by Serhiy Storchaka storch...@gmail.com: Removed file: http://bugs.python.org/file28264/smtplib_LMTP_connect_raise_err.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16647 ___

[issue16646] FTP.makeport() loses socket error details

New submission from Serhiy Storchaka: In FTP.makeport() a socket error catched and saved but then raised a new error with saved error as argument. Here is a patch which reraises an original error. -- components: Library (Lib) files: ftplib_makeport_raise_err.patch keywords: patch

[issue16646] FTP.makeport() loses socket error details

Changes by Serhiy Storchaka storch...@gmail.com: Removed file: http://bugs.python.org/file28262/ftplib_makeport_raise_err.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16646 ___

[issue16646] FTP.makeport() loses socket error details

Changes by Serhiy Storchaka storch...@gmail.com: Added file: http://bugs.python.org/file28263/ftplib_makeport_raise_err.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16646 ___

[issue16647] LMTP.connect() loses socket error details

New submission from Serhiy Storchaka: In LMTP.connect() a socket error catched and saved but then raised a new error with saved error as argument. Here is a patch which reraises an original error. -- components: Library (Lib) files: smtplib_LMTP_connect_raise_err.patch keywords: patch

[issue15982] asyncore.dispatcher does not handle windows socket error code correctly (namely WSAEWOULDBLOCK 10035)

-- components: Library (Lib) messages: 170799 nosy: McNetic priority: normal severity: normal status: open title: asyncore.dispatcher does not handle windows socket error code correctly (namely WSAEWOULDBLOCK 10035) type: behavior versions: Python 3.2

[issue15779] socket error [Errno 10013] when creating SMTP object

my log, there isn't anything abnormal that occurred just before this issue (like attempting to do the task several times at once or something). -- components: Library (Lib) messages: 169055 nosy: Jimbofbx priority: normal severity: normal status: open title: socket error [Errno 10013] when

[issue15779] socket error [Errno 10013] when creating SMTP object

Martin v. Löwis added the comment: As this is an error reported by Windows, it *very* unlikely is an issue with Python. Instead, it's a reaction that Windows produced to some sequence of events. My guess is that another process had the address in use, apparently, Windows then reports

[issue15779] socket error [Errno 10013] when creating SMTP object

James Hutchison added the comment: This is the traceback I was getting where it was just a script that simply made an SMTP connection then closed it. This fails before it attempts to connect to the server. Traceback (most recent call last): File C:\tmp\manysmtptest.py, line 8, in module

[issue15779] socket error [Errno 10013] when creating SMTP object

Martin v. Löwis added the comment: It's very easy to see why it survives a reboot. If there is a collision with some other process, that process restarts, recreating the collision. Things may depend on timing, so it may happen on some reboots and not on others (e.g. if the colliding process

[issue15779] socket error [Errno 10013] when creating SMTP object

James Hutchison added the comment: That makes no sense. Why does: s = socket.socket() s.bind(('',50007)) s.listen(1); s.close(); fix the issue then? Re-opening, this issue should be understood because having such an operation randomly fail is unacceptable for a production system. How does

[issue15779] socket error [Errno 10013] when creating SMTP object

Antoine Pitrou added the comment: s.bind(('',50007)) How did you find out 50007? Is it just a random number you chose? -- nosy: +brian.curtin, pitrou, tim.golden ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15779

[issue15779] socket error [Errno 10013] when creating SMTP object

James Hutchison added the comment: It's from the example. http://docs.python.org/library/socket.html#example -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15779 ___

[issue15779] socket error [Errno 10013] when creating SMTP object

Antoine Pitrou added the comment: According to the MSDN doc for connect(): WSAEACCES: An attempt to connect a datagram socket to broadcast address failed because setsockopt option SO_BROADCAST is not enabled. However, this implies that `getaddrinfo(host, port, 0, SOCK_STREAM)` (in

[issue15779] socket error [Errno 10013] when creating SMTP object

Antoine Pitrou added the comment: Oh, a random Google search brought the following comment from the chromium source code (it seems): “connect fails with WSAEACCES when Windows Firewall blocks the connection”. This sounds like a likelier explanation than the previous one. --

[issue15779] socket error [Errno 10013] when creating SMTP object

James Hutchison added the comment: The firewall is disabled for my machine. So the options are: 1. Port was in-use: possible except that is normally a different error 2. Port was firewalled: firewall was disabled 3. Port mis-use: not likely because this wouldn't be random 4. Port was in

[issue15779] socket error [Errno 10013] when creating SMTP object

Antoine Pitrou added the comment: By the way, please check the return value of getaddrinfo() for your SMTP server: socket.getaddrinfo(www.gmail.com, 25, 0, socket.SOCK_STREAM) [(2, 1, 6, '', ('74.125.230.213', 25)), (2, 1, 6, '', ('74.125.230.214', 25)), (10, 1, 6, '',

[issue15779] socket error [Errno 10013] when creating SMTP object

James Hutchison added the comment: I can connect to all of the IPs for my server without issue. Found this: Another possible reason for the WSAEACCES error is that when the bind function is called (on Windows NT 4.0 with SP4 and later), another application, service, or kernel mode driver is

[issue15779] socket error [Errno 10013] when creating SMTP object

Martin v. Löwis added the comment: The Python API maps nearly 1:1 to the winsock API. So the Python code literally translates to the equivalent C code (with *very* minor deviations e.g. involving the conversion of string addresses in numeric addresses). Please leave the issue closed unless

[issue15779] socket error [Errno 10013] when creating SMTP object

Changes by James Hutchison jamesghutchi...@gmail.com: -- status: closed - open ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15779 ___ ___

[issue15779] socket error [Errno 10013] when creating SMTP object

Changes by Brian Curtin br...@python.org: -- nosy: -brian.curtin ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15779 ___ ___ Python-bugs-list

[issue15779] socket error [Errno 10013] when creating SMTP object

James Hutchison added the comment: Looks to me like python grabs an outgoing port number via unrandom means and if it happens to map to a port taken by a service that demands exclusive access, then it returns the WSAEACCESS error instead of WSAEADDRINUSE. Because this is a fairly new feature

[issue15779] socket error [Errno 10013] when creating SMTP object

Changes by James Hutchison jamesghutchi...@gmail.com: -- components: +Windows ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15779 ___ ___

[issue15779] socket error [Errno 10013] when creating SMTP object

Antoine Pitrou added the comment: Looks to me like python grabs an outgoing port number via unrandom means Python does not grab an outgoing port number, its lets the OS choose one (via connect()). The only thing to watch out for would be whether you let many connections open (perhaps there's

Socket Error : Address still in use (Conveting from python 1.5.2 to 2.7.1)

Hello there, I am in the midst of converting my application from python 1.5.2 to python 2.7.1 on HP-UX 11 Itanium box. My application server will set a listening port, accepting request from multiple clients. The code just works fine in the old python environment. E.g. when I do a lsof |

[issue11136] imaplib IMAP4_SSL shutdown gets socket error in py 3.2

Changes by Antoine Pitrou pit...@free.fr: -- status: pending - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11136 ___ ___ Python-bugs-list

[issue11136] imaplib IMAP4_SSL shutdown gets socket error in py 3.2

: open title: imaplib IMAP4_SSL shutdown gets socket error in py 3.2 type: behavior versions: Python 3.2 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11136

[issue11136] imaplib IMAP4_SSL shutdown gets socket error in py 3.2

Antoine Pitrou pit...@free.fr added the comment: IMAP4_SSL.close() IMAP4_SSL.logout() IMAP4_SSL.shutdown() logout() already calls shutdown() for you and closes the socket, so you don't have to do it yourself. -- nosy: +pitrou resolution: - invalid status: open - pending

[issue6941] Socket error when launching IDLE

Terry J. Reedy tjre...@udel.edu added the comment: Download and install a current release 2.6.6, 2.7, or 3.1.2 (or 2.7.1 or 3.1.3 in a week or so). Disable or otherwise reconfigure whatever firewall or security software you have that is blocking the socket connection (as your screenshot

[issue6941] Socket error when launching IDLE

Joshua Purcell spamail.08jpurcellser...@gmail.com added the comment: Sorry I've not replied to anyones thoughts until now but nothing seems to fix it -- components: +Windows -IDLE resolution: works for me - status: closed - open ___ Python tracker

Socket error 98 Address already in use

Hi, I'm trying to make a little mp3 server / client and I'm running into a problem with the Socket error 98 Address already in use. The error doesn't happen right away, I can send 3-4 commands, disconnecting and reconnecting and they work fine and then I get this error and the client can no longer

Re: Socket error 98 Address already in use

On 06/17/2010 07:21 PM, AK wrote: Hi, I'm trying to make a little mp3 server / client and I'm running into a problem with the Socket error 98 Address already in use. The error doesn't happen right away, I can send 3-4 commands, disconnecting and reconnecting and they work fine and then I get

Re: Socket error 98 Address already in use

On 2010-06-17, AK a...@nothere.com wrote: Hi, I'm trying to make a little mp3 server / client and I'm running into a problem with the Socket error 98 Address already in use. The error doesn't happen right away, I can send 3-4 commands, disconnecting and reconnecting and they work fine

Re: Socket error 98 Address already in use

On 06/17/2010 08:19 PM, Grant Edwards wrote: On 2010-06-17, AK a...@nothere.com wrote: Hi, I'm trying to make a little mp3 server / client and I'm running into a problem with the Socket error 98 Address already in use. The error doesn't happen right away, I can send 3-4 commands, disconnecting

Re: Socket error 98 Address already in use

On 2010-06-18, AK a...@nothere.com wrote: Here it is: Traceback (most recent call last): File ./vimp3_player.py, line 112, in module Player().main() File ./vimp3_player.py, line 35, in main self.listen() File ./vimp3_player.py, line 41, in listen s.bind((HOST, PORT))

Re: Socket error 98 Address already in use

On 06/17/2010 08:59 PM, Grant Edwards wrote: On 2010-06-18, AK a...@nothere.com wrote: Here it is: Traceback (most recent call last): File ./vimp3_player.py, line 112, in module Player().main() File ./vimp3_player.py, line 35, in main self.listen() File ./vimp3_player.py,

[issue6941] Socket error when launching IDLE

Changes by Terry J. Reedy tjre...@udel.edu: -- status: pending - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6941 ___ ___

Re: Socket Error: Permission Denied (Firewall)

(corrected typos) I decided to go with outbound in McAfee. Now when I run the program, I get a long list of messages about deprecations and NumpyTest will be removed in the next release. please update code to nose or unittest. -- http://mail.python.org/mailman/listinfo/python-list

Re: Socket Error: Permission Denied

I decided to go with outbound. Now when I run the program, I get a long of messabge about deprecations and NumpyTest will be removed in the next release. please update code to nose or unittest. -- http://mail.python.org/mailman/listinfo/python-list

Re: Socket Error: Permission Denied

On Mon, Feb 8, 2010 at 7:38 PM, W. eWatson wolftra...@invalid.com wrote: I'm using McAffee. I see it was pythonw.exe blocked in red. There are several choices: Allow Access, Allow Outboubnd only Block (current), Remove Prgrm permission, Learn More. Outbound only seem reasonable, but why does

Socket Error: Permission Denied

I'm using IDLE with winxp. It seems every day I get into the Subject above. Usually, after 5-8 minutes I get past it. A msg appearing at the same time say, IDLE's subprocess didn't make connect. ... possible firewall problem. A resource for this is http://bugs.python.org/issue6941. There a

Re: Socket Error: Permission Denied

On 2/8/2010 7:24 PM, W. eWatson wrote: I'm using IDLE with winxp. It seems every day I get into the Subject above. Usually, after 5-8 minutes I get past it. A msg appearing at the same time say, IDLE's subprocess didn't make connect. ... possible firewall problem. A resource for this is

[issue6941] Socket error when launching IDLE

Changes by Kurt B. Kaiser k...@shore.net: -- status: open - pending ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6941 ___ ___ Python-bugs-list

[issue6941] Socket error when launching IDLE

adgprogramming knd_a...@yahoo.com added the comment: Thanks so much! It works perfect! There was a process running that had to do with pythonw.exe and idle.bat. My firewall also blocked access to those same programs. Thanks! -- status: pending - open

[issue6941] Socket error when launching IDLE

Kurt B. Kaiser k...@shore.net added the comment: 08jpurcell unresponsive, ignoring for now (but see suggestions below) bdouglasoz: had a firewall blocking the subprocess, apparently works for her now. I'd point out that Notepad is just an editor, IDLE gives you much more. Linux is great,

[issue6941] Socket error when launching IDLE

adgprogramming knd_a...@yahoo.com added the comment: Here is what happened to me. See the attachment. P.S.: I launched the installer and hit repair. Everything went fine in the installer, but the problem still occured. Should I upgrade to 3.11? If I have to make a change in the source code

[issue6941] Socket error when launching IDLE

adgprogramming knd_a...@yahoo.com added the comment: Oh! And my OS is Windows XP SP3 Media Center Edition Version. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6941 ___

[issue6941] Socket error when launching IDLE

Bonnie Douglas bonnie.doug...@biarri.com added the comment: The only other thing that I've done is change my firewall software. I use Bullguard. I had to use the Custom Security settings for the Firewall, but set it to always allow pythonw.exe and python.exe access to all ports. A colleague of

[issue6941] Socket error when launching IDLE

Changes by Brett Cannon br...@python.org: -- nosy: -brett.cannon ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6941 ___ ___ Python-bugs-list

[issue6941] Socket error when launching IDLE

Bonnie Douglas bonnie.doug...@biarri.com added the comment: I too seem to have experienced this same problem. I am running Windows Vista. After choosing to shut down my computer and restart without cleanly shutting down IDLE I got a socket error - socket error:connection refused when I next

[issue6941] Socket error when launching IDL

Changes by Georg Brandl ge...@python.org: -- status: open - pending ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6941 ___ ___ Python-bugs-list

[issue6941] Socket error when launching IDLE

Changes by chuck jan.hos...@gmail.com: -- status: pending - open title: Socket error when launching IDL - Socket error when launching IDLE ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6941

[issue6941] Socket error when launching IDLE

Changes by R. David Murray rdmur...@bitdance.com: -- status: open - pending ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6941 ___ ___

[issue6941] Socket error when launching IDL

. -- nosy: +brett.cannon title: Help - Socket error when launching IDL ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6941 ___ ___ Python-bugs-list mailing

Re: smtplib.SMTP throw : 'Socket error: 10053 software caused connection abort'

aberry wrote: I am using 'smtplib' module to send an email but getting exception... smtplib.SMTP(nailservernam throw error : here is trace back snippet :- smtp = smtplib.SMTP(self.server) File D:\Python24\lib\smtplib.py, line 244, in __init__ (code, msg) = self.connect(host,

smtplib.SMTP throw : 'Socket error: 10053 software caused connection abort'

I am using 'smtplib' module to send an email but getting exception... smtplib.SMTP(nailservernam throw error : here is trace back snippet :- smtp = smtplib.SMTP(self.server) File D:\Python24\lib\smtplib.py, line 244, in __init__ (code, msg) = self.connect(host, port) File

socket error: connection refused?

The first time i start the shell it always works. But often after closing it and restarting it I get: Two windows pops up and the shell, after clicking the windows the shell just closes by itself. socket error: connection refused IDLE's subprocess didnt make connection. im using python 2.5.1

Re: socket error: connection refused?

It's a security conflict. You should be able to run it again and have it work. Our company's cisco does the same thing (even after we approve the app) -- http://mail.python.org/mailman/listinfo/python-list

Re: socket error: connection refused?

On 23 Juni, 20:55, [EMAIL PROTECTED] wrote: It's a security conflict. You should be able to run it again and have it work. Our company's cisco does the same thing (even after we approve the app) doesnt work but i found out i should open the task manager and kill all the python processes, then

Re: socket error when loading the shell?

i mean vpython(www.vpython.org). tried wi5th the normal IDLE too and it worked later after i posted this but now it doesnt work again. and i havent chnaged my firewall in between. python.exe works but i want the idle not the dos-interpreter. --

Re: socket error when loading the shell?

En Mon, 31 Mar 2008 23:28:13 -0300, [EMAIL PROTECTED] escribió: tried wi5th the normal IDLE too and it worked later after i posted this but now it doesnt work again. and i havent chnaged my firewall in between. Perhaps any other running process has opened the port that IDLE uses to

socket error when loading the shell?

hi using python and wpython. when using run module or python shell on the run menu in the GUI i get socket error, connection refused. it worked before, what si wrong now? and i cant find where to start the shell directly. think i had an exe before but cant seem to find it now. -- http

Re: socket error when loading the shell?

En Sun, 30 Mar 2008 16:46:00 -0300, [EMAIL PROTECTED] escribió: using python and wpython. Soory, I don't know what wpython is when using run module or python shell on the run menu in the GUI i get socket error, connection refused. it worked before, what si wrong now? Try to detect what

Re: socket error when loading the shell?

[EMAIL PROTECTED] wrote: using python and wpython. What's wpython? when using run module or python shell on the run menu in the GUI i get socket error, connection refused. it worked before, what si wrong now? There's no process listening for the port you try to connect to, so the target

Re: IDLE Won't Start w/o Socket Error--Win XP

. ... firewall may be blocking the connection. I doubt the FW connection. There's a small X warning dialog that says Socket Error: Connection refused. Is there a way to reset IDLE? -- Wayne Watson (Nevada City, CA) Web Page: speckledwithStars.net I

Re: IDLE Won't Start w/o Socket Error--Win XP

Thanks. That did the trick. Mike Driscoll wrote: On Feb 12, 2:18 pm, W. Watson [EMAIL PROTECTED] wrote: After simply trying to write a program with help(MakeQTE), a module, and having it fail with socket errors, I decided to restart IDLE, thinking I ... I sometimes get this message when one

Re: IDLE Won't Start w/o Socket Error--Win XP

connection. ... firewall may be blocking the connection. I doubt the FW connection. There's a small X warning dialog that says Socket Error: Connection refused. Is there a way to reset IDLE? From the IDLE About box: IDLE executes Python code in a separate process, which is restarted

IDLE Won't Start w/o Socket Error--Win XP

connection. There's a small X warning dialog that says Socket Error: Connection refused. Is there a way to reset IDLE? -- Wayne Watson (Nevada City, CA) Web Page: speckledwithStars.net -- http://mail.python.org/mailman/listinfo/python-list

  1   2   >