Jeremy Banks jer...@jeremybanks.ca added the comment:
Redundant with #2706 and others.
--
nosy: -belopolsky, haypo, marketdickinson
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue4291
Jeremy Hylton jer...@alum.mit.edu added the comment:
Why did it change from 2.5 to 2.6? I'm not sure that the change makes
any sense. (Dreading the answer that I changed it...)
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org
Changes by Jeremy Hylton jer...@alum.mit.edu:
--
nosy: +jhylton
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue1659410
___
___
Python-bugs-list
Jeremy Hylton jer...@alum.mit.edu added the comment:
Committed revision 70809 (trunk). Needs to be backported.
--
nosy: +jhylton
resolution: - fixed
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue4315
Jeremy Hylton jer...@alum.mit.edu added the comment:
The current docs cover this case:
http://docs.python.org/reference/executionmodel.html#interaction-with-dynamic-features
It basically says that code compiled via exec / eval can't access free
variables.
--
resolution: - wont fix
Changes by Jeremy Hylton jer...@alum.mit.edu:
--
assignee: - jhylton
nosy: +jhylton
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue991196
Jeremy Hylton jer...@alum.mit.edu added the comment:
This code behaves as intended. The module-level execution environment
is different than other environments. The global scope and local scope
are the same dictionary. Assignments at the top-level become globals
because of this behavior
Jeremy Hylton jer...@alum.mit.edu added the comment:
I think this bug ran out of steam. Python is behaving as intended, and
I think Georg addressed all of David's questions.
--
nosy: +jhylton
resolution: - works for me
status: open - closed
Jeremy Hylton jer...@alum.mit.edu added the comment:
exec is allowed in a class statement
--
resolution: accepted - rejected
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue5578
Jeremy Hylton jer...@alum.mit.edu added the comment:
It doesn't seem helpful to leave this issue open, particularly since the
title suggest there's a problem with execfile being removed and that's
not going to change.
--
nosy: +jhylton
status: open - closed
Changes by Jeremy Hylton jer...@alum.mit.edu:
--
nosy: +jhylton
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue4199
___
___
Python-bugs-list
Changes by Jeremy Hylton jer...@alum.mit.edu:
--
priority: high - normal
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue1346238
___
___
Python-bugs
Changes by Jeremy Hylton jer...@alum.mit.edu:
--
nosy: +jhylton
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue2344
___
___
Python-bugs-list
Jeremy Hylton jer...@alum.mit.edu added the comment:
Seemed like a good idea, but no one knew how to do it.
--
resolution: - wont fix
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue2344
New submission from Jeremy Hylton jer...@alum.mit.edu:
import io
import urllib.request
f_bytes = urllib.request.urlopen(http://www.python.org/;)
f_string = io.TextIOWrapper(f_bytes, iso-8859-1)
print(f_string.read())
--
components: Library (Lib)
messages: 84840
nosy: jhylton
severity
Jeremy Hylton jer...@alum.mit.edu added the comment:
I just wanted to mention that the current head of py3k returns an
http.client.HTTPResponse and not a urllib.respone.addinfourl. That
doesn't mean it is the right thing to pass to TextIOWrapper. It's an
instance of RawIOBase
Jeremy Hylton jer...@alum.mit.edu added the comment:
The attached file is vaguely related to the current discussion. I'd
like to document the API for the urllib response, but I'd also like to
simplify the implementation on the py3k side. We can document the
simple API on the py3k side
Changes by Jeremy Hylton jer...@alum.mit.edu:
--
assignee: - jhylton
nosy: +jhylton
resolution: - accepted
type: - behavior
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue5578
Jeremy Hylton jer...@alum.mit.edu added the comment:
looks good to me
--
nosy: +jhylton
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue4962
Jeremy Hylton jer...@alum.mit.edu added the comment:
looks good to me
--
nosy: +jhylton
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue4675
Jeremy Hylton jer...@alum.mit.edu added the comment:
Seems like a reasonable feature request. I'm going to apply a variant
of the patch in 3.1 first.
--
assignee: - jhylton
nosy: +jhylton
resolution: - accepted
___
Python tracker rep
Changes by Jeremy Hylton jer...@alum.mit.edu:
--
nosy: +jhylton
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue1153027
___
___
Python-bugs-list
Changes by Jeremy Hylton jer...@alum.mit.edu:
--
nosy: +jhylton
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue918368
___
___
Python-bugs-list
Jeremy Hylton jer...@alum.mit.edu added the comment:
Indeed, I think I confused some other character encoding issues related
to HTTP with the URI issue. The discussion in RFC 3986 is length and
only occasionally clarifying for this issue. That is, it doesn't say
anything definitive like
Jeremy Hylton jer...@alum.mit.edu added the comment:
The documentation is pretty vague on this point. If you send something
other than plain ascii, it gets a bit tricky to figure out what other
headers need to be added. It would be safer for the client to pick an
encoding (e.g. utf-8
Jeremy Hylton jer...@alum.mit.edu added the comment:
Ok. Discovered that RFC 2616 says that iso-8859-1 is the default
charset, so I will use that to encode strings instead of ascii. If you
want utf-8, you could encode the string yourself before calling
request(). Presumably, you should also
Jeremy Hylton jer...@alum.mit.edu added the comment:
Committed revision 70638.
--
resolution: - fixed
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue5314
Changes by Jeremy Hylton jer...@alum.mit.edu:
--
assignee: - jhylton
nosy: +jhylton
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue5542
Jeremy Hylton jer...@alum.mit.edu added the comment:
Wow! Old issue. This behavior was present in Greg's original version
of the code.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue5542
Jeremy Hylton jer...@alum.mit.edu added the comment:
I think it makes sense to leave the socket open in this case. (In
general, I think httplib is too aggressive about closing the socket.)
I'm checking in a version for py3k, and will get around to backporting
it later.
Committed revision
Jeremy Hylton jer...@alum.mit.edu added the comment:
I'm not sure I understand the part of the code that deals with binary
strings. I agree the current behavior is odd. RFC 2396 says that
non-ascii characters must be encoded as utf-8 and then percent escaped.
In the test case you started
Jeremy Hylton jer...@alum.mit.edu added the comment:
A plausible solution is to pick some core set of functionality that we
think people need and document that API. We can modify one or both of
the current implementations to include that functionality. What do we need
Changes by Jeremy Hylton jer...@alum.mit.edu:
--
assignee: - jhylton
nosy: +jhylton
resolution: - accepted
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue5418
Jeremy Hylton jer...@alum.mit.edu added the comment:
Makes sense to me.
Committed revision 70625.
--
resolution: accepted - fixed
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue5418
Jeremy Hylton jer...@alum.mit.edu added the comment:
I'm not sure what to do here. I guess changing to utf-8 is safe insofar
as the current code only accepts ascii, so the only code that breaks
will be code that depends on the encode() call raising an exception. It
seems like the client out
Jeremy Dunck jdu...@gmail.com added the comment:
I hear you on the 2.x to 3.x transition-- I'm not really asking for
mixed-mode arithmetic. I'd be perfectly happy if float decimal raised
TypeError, as float + decimal does.
My complaint is that it is silently wrong
Jeremy Olexa darks...@gentoo.org added the comment:
I have now confirmed that the fix described here[1] works as desired. I
don't know if this is proper or not but it matches what inkblotter said.
[1]: http://www.ibm.com/developerworks/forums/thread.jspa?threadID=226339
Jeremy Olexa darks...@gentoo.org added the comment:
This also happens with Python 2.5.2 (not the latest 2.5 series, I know)
on AIX 6.1.
--
nosy: +darkside
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue4026
Jeremy Hylton jer...@alum.mit.edu added the comment:
I have a patch here that seems to work for the specific url and that
passes all the tests. Can anyone check whether it works for a larger
set of cases?
I'm a little concerned because I don't understand the new io library in
much detail
Changes by Jeremy Hylton jer...@alum.mit.edu:
--
assignee: - jhylton
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue4631
___
___
Python-bugs-list
Jeremy Hylton jer...@alum.mit.edu added the comment:
I'm sorry that I didn't notice this bug report in September! The
chunked support does exist in the http package, but it doesn't work with
urllib. Tracking in 4631.
--
nosy: +jhylton
resolution: - duplicate
status: open - closed
Jeremy Hylton jer...@alum.mit.edu added the comment:
Brief update: The Python 2.x code works because readline() is provided
by socket._fileobject. The Python 3.x code fails because it grabs the
HTTPResponse.fp instance variable at the end of
AbstractHTTPHandler.do_open. That method needs
Does the same thing happen with 2.6?
Jeremy
On Thu, Dec 11, 2008 at 8:53 AM, Jean-Paul Calderone
rep...@bugs.python.org wrote:
Jean-Paul Calderone exar...@divmod.com added the comment:
The f65 is the chunk length for the first chunk returned when
requesting that URL. A proxy could easily
Oops. I didn't think it translate the code in addinfobase to the new
style of iterators.
Jeremy
On Tue, Dec 9, 2008 at 7:50 AM, Senthil [EMAIL PROTECTED] wrote:
Senthil [EMAIL PROTECTED] added the comment:
I verified this bug in the Py3.0 and Py3.1. Shall come out with a patch
Jeremy Hylton [EMAIL PROTECTED] added the comment:
I submitted r67442, which combines the headers and body in a single
send() call. We should look at the buffering issue now, although I
probably won't have any time to check on it until Friday.
___
Python
Jeremy Hylton [EMAIL PROTECTED] added the comment:
I don't think I understand this report. The TransportSubclassTestCase
class tests the behavior of overridable methods that don't exist in
Python 3.0. Is this really a Python 3.0 problem? I'm not sure why we
expect it to work there.
Jeremy
Jeremy Hylton [EMAIL PROTECTED] added the comment:
I did the simple part of the patch, where the request and headers are
sent at the same time. The applied patch didn't pass the test suite,
and I want to think about the buffering change a bit more. It's
definitely tricky.
Jeremy
On Fri, Nov
? This accomplishes the same basic goal as
returning the header from endheaders(), but keeps the actual sending
of data encapsulated within the http connection.
Jeremy
On Tue, Nov 25, 2008 at 6:13 AM, Kristján Valur Jónsson
[EMAIL PROTECTED] wrote:
Kristján Valur Jónsson [EMAIL PROTECTED] added the comment:
I
Jeremy Hylton [EMAIL PROTECTED] added the comment:
It seems generally useful to have a helper function to replace a range
of nodes in a sequence of statements with another sequence of nodes. A
general API like that would allow you to insert or delete nodes as well
as replacing one node
could add parent pointers in the tree, right?
Jeremy
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue4327
___
___
Python-bugs-list mailing list
Unsubscribe
Jeremy Hylton [EMAIL PROTECTED] added the comment:
This patch makes sense in principle, but some of the details need to
change. The _send_output() method is used by some clients, merely
because it can be used :-(. It's fairly easy to preserve this API for
backwards compatibility.
I am also
Jeremy Hylton [EMAIL PROTECTED] added the comment:
Just wanted to mention that the best solution is to update as much code
as possible to use HTTPConnection instead of HTTP. I'm not sure how
easy it is to do for xmlrpclib, since it exposes methods like
send_content(). I guess we can preserve
Jeremy Hylton [EMAIL PROTECTED] added the comment:
I haven't thought about the code in a while, but what code that
modifies the AST are we worried about? There are lots of
modifications in ast.c, since it is being created there. The case we
really care about is sequences, where we want
for efficiency.
Jeremy
On Mon, Nov 24, 2008 at 12:32 PM, Jeremy Hylton [EMAIL PROTECTED] wrote:
Jeremy Hylton [EMAIL PROTECTED] added the comment:
This patch makes sense in principle, but some of the details need to
change. The _send_output() method is used by some clients, merely
because it can
Jeremy Hylton [EMAIL PROTECTED] added the comment:
Python 2.4 is now in security-fix-only mode. No new features are being
added, and bugs are not fixed anymore unless they affect the stability
and security of the interpreter, or of Python applications.
http://www.python.org/download/releases
Jeremy Banks [EMAIL PROTECTED] added the comment:
Sorry, allowing for conversion to int/float is probably a more sensible
solution.
This idea was brought to my mind when I was making a very very simple
script for a friend to display how far through a time range we currently
are. For example
New submission from Jeremy Banks [EMAIL PROTECTED]:
It would be convenient if it were possible to divide one
datetime.timedelta object by another to determine their relative durations.
Were the datetime module pure Python a crude solution would just be to
add two methods like this:
def
Jeremy Banks [EMAIL PROTECTED] added the comment:
Thanks, I should have paid more attention to the results when I searched
for duplicates. I think that Christian's suggestion of enabling float()
and int() for timedeltas is worth having here, though.
--
nosy: -christian.heimes
Jeremy Hylton [EMAIL PROTECTED] added the comment:
Committed revision 65118.
I applied a simple version of this patch and added a unittest.
--
assignee: - jhylton
nosy: +jhylton
status: open - closed
___
Python tracker [EMAIL PROTECTED]
http
Changes by Jeremy Hylton [EMAIL PROTECTED]:
--
assignee: - jhylton
nosy: +jhylton
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue3377
___
___
Python
Jeremy Hylton [EMAIL PROTECTED] added the comment:
Oops. Let me look at this tomorrow. It was down to one failing test
that last time I checked.
Jeremy
On Wed, Jun 11, 2008 at 10:10 PM, Barry A. Warsaw
[EMAIL PROTECTED] wrote:
Barry A. Warsaw [EMAIL PROTECTED] added the comment
Jeremy Thurgood [EMAIL PROTECTED] added the comment:
This looks very much like a duplicate of issue 1714. Perhaps the two
should be merged?
--
nosy: +jerith
_
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1524825
Jeremy Hylton [EMAIL PROTECTED] added the comment:
I think we should move robotparser into the urllib package. Anyone
disagree?
Jeremy
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2775
Jeremy Thurgood [EMAIL PROTECTED] added the comment:
Added handling for Expect: 100-continue header to
BaseHTTPRequestHandler. By default, any request that has this header
gets a 100 Continue response (with no other headers) before
do_WHATEVER() is called. By overriding handle_expect_100(), you
Jeremy Thurgood [EMAIL PROTECTED] added the comment:
The above patch adds a set of tests for BaseHTTPServer, although the
only tests actually written were those around the areas touched by the
work done for this issue.
__
Tracker [EMAIL PROTECTED]
http
Changes by Jeremy Hylton [EMAIL PROTECTED]:
--
nosy: +jhylton
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1348
__
___
Python-bugs-list mailing list
Unsubscribe
Changes by Jeremy Hylton [EMAIL PROTECTED]:
--
nosy: +jhylton
_
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1346238
_
___
Python-bugs-list mailing list
Jeremy Hylton [EMAIL PROTECTED] added the comment:
I'm working on the new urllib package.
--
nosy: +jhylton
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2775
New submission from Jeremy Dunck [EMAIL PROTECTED]:
Within python 2.5.2:
from decimal import Decimal
x = 3.0
y = Decimal('0.25')
x y
False (expected error, as in 2.4, or True)
--
components: Library (Lib)
messages: 64827
nosy: jdunck
severity: normal
status: open
title: float
Changes by Jeremy Dunck [EMAIL PROTECTED]:
--
type: - behavior
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2531
__
___
Python-bugs-list mailing list
Unsubscribe
of terminology, there is no currying going on. It's
just a problem with closures.
Jeremy
On 10/1/06, Scott Marks [EMAIL PROTECTED] wrote:
The code below exhibits different behavior depending on whether it invokes
sys.settrace ('-t' option) or not. This means that (in a more complicated
case) debugging
I'm working on this bug now, but can't get an SF login to update the bug report.
Jeremy
On 10/3/06, SourceForge.net [EMAIL PROTECTED] wrote:
Bugs item #1569998, was opened at 2006-10-03 14:04
Message generated for change (Settings changed) made by gbrandl
You can respond by visiting:
https
501 - 572 of 572 matches
Mail list logo
