R. David Murray added the comment:
Oh, yes, and it is likely to be important to know what OS you are on. I tested
on linux.
--
___
Python tracker
<http://bugs.python.org/issue10
Changes by R. David Murray :
--
stage: -> patch review
type: -> feature request
versions: +Python 3.3 -Python 2.6, Python 3.0
___
Python tracker
<http://bugs.python.org/
R. David Murray added the comment:
Since 2.7 has been released and this behaviour could not be changed in a point
release even if agreement that it was a good change was reached, and since it
is meaningless in 3.x, I'm closing this issue.
--
nosy: +r.david.murray
resol
R. David Murray added the comment:
Looks like Josiah just forgot to close this bug, so I'm closing it.
--
nosy: +r.david.murray
stage: -> committed/rejected
status: open -> closed
___
Python tracker
<http://bugs.python
R. David Murray added the comment:
No idea if this is even still valid (I skimmed the issue, I did not try to
understand it in detail), but I agree that a change like this is more feature
than bug fix, so I'm updating the issue settings accordingly.
--
nosy: +r.david.murray
Changes by R. David Murray :
--
type: -> feature request
versions: +Python 3.3
___
Python tracker
<http://bugs.python.org/issue4264>
___
___
Python-bugs-lis
R. David Murray added the comment:
Indeed, the time module is documented as not handling timestamps before the
epoch.
--
nosy: +r.david.murray
resolution: -> invalid
stage: -> committed/rejected
status: open -> closed
___
Python track
Changes by R. David Murray :
--
resolution: -> invalid
stage: -> committed/rejected
status: open -> closed
___
Python tracker
<http://bugs.python.o
R. David Murray added the comment:
Since the os functions tend to be small wrappers around system functions, this
sounds like it is probably a platform issue and not a Python issue. I'm adding
our windows experts as nosy, they can reopen the issue if they disagree.
--
R. David Murray added the comment:
I'm not sure what "compiling using a user prefix" means. I've certainly
specified a prefix containing my home directory and had things work just fine.
There isn't enough information here to know what is actually going wrong.
Sinc
R. David Murray added the comment:
It's too late to make any further changes in version numbers for 2.x. Sorry
this slipped by me.
--
status: open -> closed
___
Python tracker
<http://bugs.python.or
R. David Murray added the comment:
Leaving the input unchanged does seem to be what browsers do. (Issue 7626 has
some info on browser behaviour with invalid entity refs.)
Rather than pre-validating the input, I think the exception can be caught and
the putative entity returned unchanged
R. David Murray added the comment:
Ah, as an undocumented internal interface it may in fact not be appropriate to
make this change. Or it may be. I'll have to look at the code in more detail
to figure that out, or perhaps Senthil will. (It may even be time to document
the function,
R. David Murray added the comment:
Note that this is a regression relative to 2.6, where the same call returns ''
(which is different from what it returns on linux, where the result would be
'%f', or OSX, where the result would be 'f'). (Tests done on windows XP
R. David Murray added the comment:
Yes, adding the x- version would probably be pointless as most likely nobody
uses it.
Has anyone found any definitive info on where exactly in the approval process
image/svg+xml is?
I think we should probably just go ahead and put it in, but it would be
R. David Murray added the comment:
No, I don't think it qualifies as a common_type.
But since this is technically a feature request we need Georg's approval for
the commit.
--
___
Python tracker
<http://bugs.python.o
R. David Murray added the comment:
It is used in the tests, but I agree that it doesn't appear to be used in the
code. I've removed the misleading comment and marked the self.handlers
attribute as backward-compat-only in r87448, r87449, and r87450.
The sorting is based on a
R. David Murray added the comment:
Committed a slightly different patch in r87451, with tests. Although I do
consider this a bug fix, it hasn't apparently caused any problems in real life
and does represent a slight behavior change, so I'm not backporting it.
--
R. David Murray added the comment:
Got approval from Georg on IRC, so go ahead and commit it, Terry. Or assign it
to me if you'd rather I do it.
--
___
Python tracker
<http://bugs.python.org/is
R. David Murray added the comment:
Reading the RFC again, I think you are right. The quoted vs unquoted sounds
like it refers to the *n vs the [*n]* forms, and the latter doesn't use quoted
strings but % encoding.
I'm attaching a patch that adds some tests and fixes this. It
R. David Murray added the comment:
I take it back. Previously quotes didn't get added if they weren't already
there. So my simpleminded fix may not be the best choice.
--
___
Python tracker
<http://bugs.python.org
R. David Murray added the comment:
Well, if the parameters aren't part of the path info, what are they part of?
They are passed as part of path info now, just incorrectly encoded. I haven't
found anything so far to make me think they belong any
Changes by R. David Murray :
--
nosy: +benjamin.peterson
stage: -> needs patch
versions: +Python 3.3
___
Python tracker
<http://bugs.python.org/issu
R. David Murray added the comment:
Where is this example?
--
assignee: -> d...@python
components: +Documentation
nosy: +d...@python, r.david.murray
type: crash -> behavior
___
Python tracker
<http://bugs.python.org/i
Changes by R. David Murray :
--
assignee: d...@python ->
components: -Documentation
keywords: +easy
nosy: -d...@python
stage: -> unit test needed
___
Python tracker
<http://bugs.python.org/i
R. David Murray added the comment:
No, I was wrong. This would only be an issue when a parameter's value is
changed, and at that point we should be producing correctly (un)quoted values
no matter what the original quoting of the individual value was.
So I've applied the patch
R. David Murray added the comment:
I suspect it would help if there are more changes, though.
I believe that to push to launchpad you have to upload an ssh key. Not sure
why you'd get "no such account", though. Barry woul
R. David Murray added the comment:
Yes, I think it is a good idea for site.py to issue error messages and continue
on when it is processing files that don't come from the python distribution
itself (such as pth files). However, I think just printing the error message
is not going to pr
R. David Murray added the comment:
Georg posted a patch to issue 5258 that would "fix" this. I've posted a
counter proposal that would give more info. We're proposing to simply write to
stderr and then continue. With either patch this issue would be fixed, so I
Changes by R. David Murray :
--
nosy: +Arfrever, dwr2, eric.araujo, haypo, tarek
___
Python tracker
<http://bugs.python.org/issue5258>
___
___
Python-bugs-list m
R. David Murray added the comment:
Yes, I forgot to delete that bit when I realized it could all be done in one
place.
--
___
Python tracker
<http://bugs.python.org/issue5
R. David Murray added the comment:
See also msg79724 of issue 4871. From looking at the code it appears that the
filename must be a string, and if it contains only ASCII characters it is
entered as ascii, while if it contains non-ascii it is encoded to utf-8 and the
appropriate flag bits
R. David Murray added the comment:
Here is a revised patch with tests.
--
Added file: http://bugs.python.org/file20169/site_pth_exceptions.diff
___
Python tracker
<http://bugs.python.org/issue5
New submission from R. David Murray :
assertRaises used as a method can't take a msg keyword argument because all
args and keywords are passed to the callable. But in context manager form it
could, and this can be useful. See, for example, issue 3583.
--
keywords: easy
mes
R. David Murray added the comment:
I think the best we can do here is add a message explaining that the error may
be due to a broken DNS server (one with a wildcard dns record for all
non-existent top level domains). However, assertRaises, even in context
manager form, doesn't take
R. David Murray added the comment:
IMO there's no way to fix this. I suggest closing it as invalid, since the
problem is a buggy ISP DNS server, and the problem only occurs when
time.xmlrpc.com is down.
The canonical fix to problems like this is to remove dependency on the external
se
R. David Murray added the comment:
Committed to py3k in r87497, 3.1 in r87499, and 2.7 in r87500.
--
resolution: -> fixed
stage: patch review -> committed/rejected
status: open -> closed
___
Python tracker
<http://bugs.python.o
R. David Murray added the comment:
OK, I'm reopening this as a doc issue, since currently the Python3 writer docs
do not mention newline='', and it is indeed required on Windows. John, would
you care to suggest a doc patch?
I agree with Skip that "where it makes a
R. David Murray added the comment:
Well, this is the same
treat-strings-and-byte-strings-equivalently-in-the-same-API problem that we've
had elsewhere. It'll require a bit of refactoring to make it work.
On read zipfile decodes filenames using cp437 if the utf-8 flag isn't s
R. David Murray added the comment:
I've considered this a bit more deeply, and it turns out to be simpler to fix
than I originally thought, assuming the fix is acceptable.
When a message is parsed we obviously wind up with headers that don't have any
embedding issues. So, if we
R. David Murray added the comment:
I never forward ported this, but it was fixed in a different way in python3
during a complete rewrite of transient_internet for other reasons.
--
resolution: -> fixed
stage: commit review -> committed/rejected
status: open -&g
R. David Murray added the comment:
Too late for 3.2, will implement for 3.3.
--
title: The email package should defer to the codecs module for all aliases ->
The email package should defer to the codecs module for all aliases
versions: +Python 3.3 -Python
R. David Murray added the comment:
Now that we are primarily focused on Python3 development, collecting "unicode"
issues is not really all that useful (at least not to me, and I'm currently
doing the email maintenance), so I'm closing this. All the relevant issues are
a
R. David Murray added the comment:
Since this is a performance hack and is considerably invasive of the feedparser
code (and needs updating), I'm deferring it to 3.3.
--
stage: unit test needed -> patch review
versions: +Python 3.3 -Python 2.7, Python 3.1, Py
Changes by R. David Murray :
--
versions: +Python 3.3 -Python 3.2
___
Python tracker
<http://bugs.python.org/issue3244>
___
___
Python-bugs-list mailing list
Unsub
R. David Murray added the comment:
Somehow I missed this in my pre-beta feature request review :(
--
versions: +Python 3.3 -Python 3.2
___
Python tracker
<http://bugs.python.org/issue1162
Changes by R. David Murray :
--
versions: +Python 3.3 -Python 3.2
___
Python tracker
<http://bugs.python.org/issue9864>
___
___
Python-bugs-list mailing list
Unsub
Changes by R. David Murray :
--
versions: +Python 3.3 -Python 3.2
___
Python tracker
<http://bugs.python.org/issue1043706>
___
___
Python-bugs-list mailin
R. David Murray added the comment:
The skip was added and the service is back and has been for a while, so I'm
closing this, but see also issue 6027.
--
resolution: -> out of date
stage: patch review -> committed/rejected
status: ope
Changes by R. David Murray :
--
versions: +Python 3.3 -Python 3.2
___
Python tracker
<http://bugs.python.org/issue740495>
___
___
Python-bugs-list mailin
Changes by R. David Murray :
--
versions: +Python 3.3 -Python 3.2
___
Python tracker
<http://bugs.python.org/issue634412>
___
___
Python-bugs-list mailin
Changes by R. David Murray :
--
versions: +Python 3.3 -Python 2.7
___
Python tracker
<http://bugs.python.org/issue795081>
___
___
Python-bugs-list mailin
Changes by R. David Murray :
--
versions: +Python 3.1, Python 3.2
___
Python tracker
<http://bugs.python.org/issue1025395>
___
___
Python-bugs-list mailin
Changes by R. David Murray :
--
versions: +Python 3.1, Python 3.2
___
Python tracker
<http://bugs.python.org/issue8769>
___
___
Python-bugs-list mailing list
Unsub
Changes by R. David Murray :
--
versions: +Python 3.1, Python 3.2
___
Python tracker
<http://bugs.python.org/issue9967>
___
___
Python-bugs-list mailing list
Unsub
Changes by R. David Murray :
--
versions: +Python 3.2
___
Python tracker
<http://bugs.python.org/issue9298>
___
___
Python-bugs-list mailing list
Unsubscribe:
R. David Murray added the comment:
If the RFC says they are safe it seems like we should include them in the safe
list.
--
___
Python tracker
<http://bugs.python.org/issue10
R. David Murray added the comment:
Committed to 2.7 in r87515. On second thought there's no reason to forward
port the test because Python3 doesn't have the equivalent type-promotion issues.
--
nosy: -BreamoreBoy
resolution: -> fixed
stage: patch review -> committed
R. David Murray added the comment:
Committed (redid, actually) 2nd patch in r87516. I may or may not backport it.
--
resolution: -> fixed
stage: patch review -> committed/rejected
status: open -> closed
versions: -Python 2.6, Python 2.7, P
R. David Murray added the comment:
But clearly intentional, and now enshrined in released code.
--
nosy: +mark.dickinson, r.david.murray
resolution: -> invalid
stage: -> committed/rejected
status: open -> closed
___
Python track
R. David Murray added the comment:
LazyImporter isn't used in Python3. Without someone motivated to propose a
patch this isn't going to be changed, so I'm closing the issue.
--
resolution: -> wont fix
stage: -> committed/rejected
s
R. David Murray added the comment:
>>> struct.pack('2s', 'ha')
b'ha'
>>> struct.pack('2s', 'hé')
b'h\xc3'
>>> struct.pack('3s', 'h
R. David Murray added the comment:
Parser is a legacy API, and message_from_string (which uses it) is just a
convenience function. If performance is an issue for your application, call
feedparser directly and optimize the feeding to suit your application.
--
resolution: -> wont
R. David Murray added the comment:
As far as I can tell it is simply wrong per-RFC to put a charset parameter on a
mulitpart content-type. So I think this should, indeed, raise an error on the
Multipart subtype.
If someone sets any charset, the CTE is set wrong. So code that sets charset
R. David Murray added the comment:
Since set_charset should not be valid on a multipart, I don't see a reason to
have a separate issue for the post-attach case.
Also, although I haven't searched the RFCs, I don't think we can assume that
set_chaset is valid only on text pa
Changes by R. David Murray :
--
keywords: +easy
nosy: +michael.foord
versions: +Python 2.7, Python 3.1, Python 3.2 -Python 2.6
___
Python tracker
<http://bugs.python.org/issue10
R. David Murray added the comment:
See also issue 6533.
--
___
Python tracker
<http://bugs.python.org/issue6027>
___
___
Python-bugs-list mailing list
Unsub
R. David Murray added the comment:
Committed to py3k in r87550. Since the only application that would trip up
would be one not using SimpleCookie to read SimpleCookie generated cookies
*and* that doesn't implement unescaping (in which case it wasn't really
handling SimpleCookie co
R. David Murray added the comment:
In this case I think it is safe enough, since it only results in the ;,= not
getting encoded. If an application were doing anything with the encoded chars,
it would probably be decoding them, and now that step will simply become a
noop. Of course
New submission from R. David Murray :
Working on issue 10686, I've discovered that the logic for charset conversion
in email.header.Header.append is bogus. It happens to work for most charsets
because for most charsets the input codec and the output codec are the same.
For shift_ji
Changes by R. David Murray :
--
nosy: +barry
___
Python tracker
<http://bugs.python.org/issue10790>
___
___
Python-bugs-list mailing list
Unsubscribe:
R. David Murray added the comment:
Updated patch that also fixes the docs.
--
Added file: http://bugs.python.org/file20189/header_append.patch
___
Python tracker
<http://bugs.python.org/issue10
R. David Murray added the comment:
Since GZipFile inherits from BufferedIOBase, and TextIOWrapper is supposed to
be designed to wrap a BufferedIOBase object, I would say yes it ought to work.
On the other hand there may also be a doc error there, since it may be that
TextIOWrapper actually
R. David Murray added the comment:
Oops. It only has that inheritance in 3.2.
--
versions: -Python 2.7, Python 3.1
___
Python tracker
<http://bugs.python.org/issue10
R. David Murray added the comment:
Heh, and 2.7. Fixing versions yet again.
--
versions: +Python 2.7
___
Python tracker
<http://bugs.python.org/issue10
R. David Murray added the comment:
bz2 is a pure C module, so that's a very different situation.
--
___
Python tracker
<http://bugs.python.org/is
R. David Murray added the comment:
Right, but in the bz2 case I think it is a feature request rather than a
bugfix. In any case it should be a separate issue.
--
___
Python tracker
<http://bugs.python.org/issue10
R. David Murray added the comment:
One way to "fix" this would be to have make test run the tests with -j1 and
pass in the -S and -s flags, and then have regrtest special case test_site and
remove those flags for the run of that single test.
An interesting facet of this proposal
R. David Murray added the comment:
Here is a proof of concept patch if anyone wants to play with it.Note that
a higher value could be used for the j option; multiple threads help even on
uniprocessor systems since a bunch of the tests spend time waiting around.
The patch removes the
R. David Murray added the comment:
Applied in r87590. I threw in an extra test for a multi-leapyear-range. Since
there was no reason not to, I backported it to 3.1 in r87591 and 2.7 in r87592.
In the latter two commits I also backported the issue 9342 patch.
Thanks for the patch, John
R. David Murray added the comment:
Backported it to 3.1 in r87591 and 2.7 in r87592 along with the patch for issue
9361.
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/issue9
R. David Murray added the comment:
I finally got around to researching this issue in the tracker.
Issue 10298 is a close relative to this issue. The fix from that issue make
the test that Xuanji added here pass. That issue contains no testsit would
be ideal to have tests that test the
R. David Murray added the comment:
FWIW, having just looked at related code in zipfile recently, this patch looks
correct to me.
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/issue10
R. David Murray added the comment:
Thank you very much for working on this! I'll try to take a look at the patch
soon. A couple quick comments based on your posting: first, the email module
now has a BytesFeedparser that will accept a byte stream, which I hope might
simplify your
R. David Murray added the comment:
Dev: I have no idea how what you just posted relates to the subject of this
issue. Could you clarify please?
--
___
Python tracker
<http://bugs.python.org/issue10
R. David Murray added the comment:
Etienne: since this is about solving a 3.x specific problem, it will not get
backported. Issue 1573931 looks unrelated to me at a quick glance. FYI, you
will find that you *do* have detach in 2.7 if you open a file using the io
subsystem (import io). Of
R. David Murray added the comment:
Yes, that is my suggestion. Keep in mind that I haven't looked at the patch or
run any tests yet :)
If windows-specific hacks are needed to get the binary stream in 3.x, then IMO
that's a bug in IO. As far as I know at the moment there
R. David Murray added the comment:
Yeah, making a generic way to put specific tests into a subprocess run sounds
like a better solution.
But...
The xml error in test___all__ is due to the fact that test___all__ imports
site. So even with the above we'd need to special case si
R. David Murray added the comment:
Ah, I hadn't looked closely enough at site.py to realize that the init work was
being done by a 'main()' call. Given that, just moving the main call out
should be relatively unlikely to break any custom site.py. Worse case would
pre
R. David Murray added the comment:
The hanging test still hangs for me with _VERBOSE set to True on py3k trunk.
--
resolution: fixed ->
status: closed -> open
___
Python tracker
<http://bugs.python.org/
R. David Murray added the comment:
Agreed that the original issue is invalid. So either the title should be
changed so it can be used to address Martin's question, or it should be closed.
--
nosy: +r.david.murray
___
Python tracker
R. David Murray added the comment:
Have you tried 3.2b2?
--
nosy: +haypo, r.david.murray
type: -> behavior
___
Python tracker
<http://bugs.python.org/issu
R. David Murray added the comment:
Committed to py3k in r87750 and 3.1 in r87751.
--
resolution: -> fixed
stage: patch review -> committed/rejected
status: open -> closed
___
Python tracker
<http://bugs.python.or
R. David Murray added the comment:
A day late, but I've looked at the patch.
Now, I'm not all that knowledgeable about CGI, so other people will probably
want to chime in here
First, I'm uploading a new version of the patch as an svn diff (can be applied
to a checkout u
R. David Murray added the comment:
Here is a modified version of the unittest file from unittest.zip that can be
run against Pierre's code (it feeds FieldStorage a text stream with a buffer).
Running the tests require the data files from the zip.
They do not pass, in a very differen
R. David Murray added the comment:
Yeah, the documentation for the email stuff is in the dev docs. There's a
short summary in the changes section of the email intro with links to the
classes and methods that are affected. But basically you call BinaryFeedParser
and feed it a binary
R. David Murray added the comment:
Another alternative might be to return "None" ("refuse the temptation to
guess"). But, given the long standing nature of the current guessing, having
it return the specific version string may indeed make sense.
--
Changes by R. David Murray :
--
nosy: +ncoghlan
___
Python tracker
<http://bugs.python.org/issue10835>
___
___
Python-bugs-list mailing list
Unsubscribe:
R. David Murray added the comment:
Well, the digits are there if they are there in the name when that's actually
what is in argv[0], so as long as that's the name the binary is actually
installed under I don't think it will break anything. I presume the same
applies to th
R. David Murray added the comment:
The behaviour you observe is by design, and documented. The email package
needs to be able to handle RFC-invalid input, which includes messages with
multiple instances of fields that are supposed to be singletons. It also needs
to keep track of the order
3601 - 3700 of 12938 matches
Mail list logo