This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author demian.brecht
Recipients berker.peksag, demian.brecht, flox, loewis, mcjeff, polymorphm
Date 2014-12-17.00:17:28
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1418775448.92.0.528808090168.issue14134@psf.upfronthosting.co.za>
In-reply-to
Content
I think we've started to venture into system-level territory that the standard library itself shouldn't have to account for. If TCP on systems are configured by default to allow for infinite timeouts, then it should likely be an issue for those distros. I don't think accounting for such things should be the responsibility of the standard library. The socket module behaves appropriately in handing off timeouts to be managed by the system level if left undefined. I think that any further discussion around timeouts should be taken up on distro mailing lists, or even perhaps python-list as it's not directly relevant to this issue.

As for this specific issue, unless someone beats me to it, I'll get a patch together introducing the session_factory as soon as I can.
History
Date User Action Args
2014-12-17 00:17:28demian.brechtsetrecipients: + demian.brecht, loewis, flox, mcjeff, polymorphm, berker.peksag
2014-12-17 00:17:28demian.brechtsetmessageid: <1418775448.92.0.528808090168.issue14134@psf.upfronthosting.co.za>
2014-12-17 00:17:28demian.brechtlinkissue14134 messages
2014-12-17 00:17:28demian.brechtcreate