Jon Nelson

Show:

What's happening?

  • flesh out MANIFEST.in and setup.cfg

    Out of the box, 0.6 does not build rpms properly. The following fixes that (and probably fixes a number of other distutils-related issues). Strictly, using MANIFEST.in should probably be preferred to shipping MANIFEST, as the latter is auto-generated from MANIFEST.in - therefore, IMO subsequent releases need not include MANIFEST diff -urN docutils-0.6.orig/MANIFEST.in...

    2009-10-19 14:18:18 UTC in Docutils: Documentation Utilities

  • Comment: 5 range support waits on keepalive timeout [2]

    Yes, it turns out to have been a server bug, and has nothing to do with range requests. However, your followup doesn't address points 1 or 3 above. As I see it, curl (the binary) is a convenient user interface to libcurl. *curl* knows which request is the last, and it can tell libcurl to issue the connection: close header. The rfc is pretty clear that this is a "should" and not a "must".

    2009-10-14 04:05:11 UTC in curl and libcurl

  • 5 range support waits on keepalive timeout [2]

    Sorry for creating a duplicate bug, but I've tried and I can't figure out how to re-open an issue (or even comment on an existing one!) Specifically, I'm talking about: range support waits on keepalive timeout - ID: 2853575 I'll reproduce the relevant bits here: me: If one issues a range request, the Connection: close header *should* be sent but it is not. Since the default...

    2009-10-13 16:51:26 UTC in curl and libcurl

  • range support waits on keepalive timeout

    If one issues a range request, the Connection: close header *should* be sent but it is not. Since the default protocol is http/1.1, what happens is that curl makes a (perfectly valid!) request without any "Connection" header, which in http/1.1 normally indicates a passive request for keep-alive. When the server is done completing the response, it will hold the socket open and wait for more...

    2009-09-07 14:13:05 UTC in curl and libcurl

  • connect reset by peer from some locations

    I'm having difficulting with yro.slashdot.org, apple.slashdot.org, and mobile.slashdot.org - but not with slashdot.org, rss.slashdot.org, linux.slashdot.org. It's not firefox, and it's not a firewall issue - this happens with telnet, wget, curl, everything, and from 3 different hosts, geographically across the US, using totally different software loads, ISPs, etc... This is what I get with...

    2009-06-01 17:55:51 UTC in Slash

  • would like boa-devel shut down/removed please

    I would like to have the boa-devel mailing list shut down and removed. If the archives could be made available to me beforehand, that would be awesome. Thanks!

    2007-07-07 03:07:38 UTC in SourceForge.net

  • crash in longobject (invalid memory access)

    While debugging a memory consumption problem, I disable pymalloc and found a crasher in longobject.c, line 2518 (Python 2.4.1). The code currently reads: Py_XDECREF(a); Py_XDECREF(b); Py_XDECREF(c); Py_XDECREF(temp); if (b->ob_size > FIVEARY_CUTOFF) { for (i = 0; i < 32; ++i) Py_XDECREF(table[i]); } return (PyObject *)z; It...

    2005-10-05 20:03:18 UTC in Python

  • Followup: RE: Boa and image theft

    I don't think so.

    2005-01-26 21:47:55 UTC in Boa

  • Followup: RE: Boa and XML/RPC/SOAP

    Yes. If /RPC2 points to a CGI.

    2005-01-26 21:47:35 UTC in Boa

  • Comment: Python 2.3+ socket._fileobject handles EAGAIN with data loss

    Logged In: YES user_id=8446 An improvement would be to allow EAGAIN to surface only if it happens as the /first/ read.

    2004-10-01 18:25:43 UTC in Python

About Me


Send me a message

My Projects