R. David Murray added the comment:
Victor: in the production code discussed in the original posting, there *are*
line numbers, and they are meaningful; they just aren't monotonically
increasing.
I believe the request here is to simply remove the assert. (If we did that,
we'd ha
R. David Murray added the comment:
The patch looks correct to me, but we also need tests.
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/issue21
R. David Murray added the comment:
I'd prefer to get rid of it, otherwise we might get requests to add all the
other os.path functions to the shutil namespace, and I don't think having that
kind of "more than one way to do it" serves anyone. I suppose we'll have to
R. David Murray added the comment:
'below' doesn't make sense at all if you view it via pydoc. There is only one
unsafe function left, mktemp. Here is an alternate patch that takes advantage
of that fact.
--
nosy: +r.david.murray
Added file: http://bugs.python.org/fil
R. David Murray added the comment:
Milan: using 'localhost' is incorrect, since the string 'localhost' will not
always resolve to the local host IP, while passing None to getaddrinfo will.
It is significant that the example fails. We need a test for this case (the
R. David Murray added the comment:
OK, I've finally had time to review this, sorry for the delay.
The impalib mechanism is tailored to how imap works (that's the whole thing
about "continuation response". smtplib auth works a bit differently, and your
adaptation
R. David Murray added the comment:
Aren't things like this normally accomplished by editing Modules/Setup?
Granted, that's not the most convenient build API...
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.o
Changes by R. David Murray :
--
resolution: -> not a bug
stage: -> resolved
status: open -> closed
___
Python tracker
<http://bugs.python.or
R. David Murray added the comment:
"Note that split will never split a string on an empty pattern match"
You can get what you want this way:
>>> re.split(r'(\w*)', 'a funky string')
['', 'a', ' ', 'funky', ' &
R. David Murray added the comment:
Yes, this will be fixed in 3.5 one way or another.
--
___
Python tracker
<http://bugs.python.org/issue19662>
___
___
Python-bug
R. David Murray added the comment:
Yes, this is a recent enhancement and the example was not updated to match.
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/issue21
R. David Murray added the comment:
Issue number was mistyped in commit message. Commit was 730eeb10cd81.
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/issue21
R. David Murray added the comment:
This is likely to be hard to reproduce (but perhaps someone will try). The best
hope of getting it fixed is probably for you to investigate it yourself.
Were you using ssl? Also, have you tried all the python versions you selected,
and if so, which exact
R. David Murray added the comment:
Added review comments.
--
___
Python tracker
<http://bugs.python.org/issue19662>
___
___
Python-bugs-list mailing list
Unsub
R. David Murray added the comment:
I think the code should be using 'detach' after passing the fp to parser.parse,
instead of using 'with'.
--
versions: +Python 3.5 -Python 3.3
___
Python tracker
<http://bug
R. David Murray added the comment:
Personally I think the fact that this doesn't work by default is a bug in
unittest. See issue 15007. Issue 16662 may also be related.
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.py
R. David Murray added the comment:
I think the answer is that if you want that level of control you can't use
communicate, you have to implement what you specifically need.
I'm going to close this as rejected. It could be reopened if someone can find
a way to propose something
Changes by R. David Murray :
--
type: crash -> behavior
___
Python tracker
<http://bugs.python.org/issue21516>
___
___
Python-bugs-list mailing list
Unsubscrib
R. David Murray added the comment:
Right, part of the parser contract is to not throw exceptions. Traditionally,
a bug could result in an exception, but not an invalid message.
However, using the new email policies, it is possible to *request* that it
raise exceptions instead of registering
R. David Murray added the comment:
If I put a 'print("one iteration") at the top of the loop, that string is
printed exactly once. I presume you realized that and that is why you closed
this?
--
nosy: +r.david.murray
resolution
R. David Murray added the comment:
Oh, this is the same code as in issue 21630 that you closed. Since the loop is
only executed once (as confirmed by adding a print), I suspect you have a bug
in your expectations of the output :)
--
nosy: +r.david.murray
Changes by R. David Murray :
--
keywords: +easy
___
Python tracker
<http://bugs.python.org/issue21548>
___
___
Python-bugs-list mailing list
Unsubscribe:
R. David Murray added the comment:
My idea (which I haven't worked out in detail) is to add either a new content
manager that extends raw_data_manager, or just add to raw_data_manager, a
handler for 'multipart/related'. The set handler would handle a value of type
'dic
R. David Murray added the comment:
Your second bullet item would seem to me to be the obvious interpretation of
the docs. This is, after all, Python, so 'integer' would refer to Python
integers and their operations. So I agree with Stefan that the docs are
correct as they stand.
R. David Murray added the comment:
There is also an option to make less quit if enter is pressed on the last line
(-e/--quit-at-eof).
These more beginner friendly options could be provided by pydoc if there is no
existing PAGER or LESS environment variable.
--
nosy: +r.david.murray
R. David Murray added the comment:
You may not be a noob, but on the other hand we can't see the bug. So your
best bet would be to post your code to the python-list mailing list and ask for
help refining your bug report into something we can take acti
R. David Murray added the comment:
I get an exception. I think you need to be more careful with your testing.
Please take this to python-list for further help.
--
___
Python tracker
<http://bugs.python.org/issue21
R. David Murray added the comment:
I suspect this is either related to or is a duplicate of issue 1823.
--
___
Python tracker
<http://bugs.python.org/issue21
R. David Murray added the comment:
A side note about tests: once a couple or three years ago I made it so that you
could run 'make doctest' against the turtle documentation and it would work
(displaying stuff on the screen). There's no checking of the output, but it
proved
R. David Murray added the comment:
"Integers are outside a required range" makes me wonder why it isn't a
ValueError. An OverflowError should be the result of a *computation*, IMO, not
a bounds check.
So, maybe add your sentence with the additional phrase "for
R. David Murray added the comment:
In python, everything is references to objects. So yes, this is expected
Python behavior. Issue 20135 is about improving the FAQ entries on this
subject, so I'm closing this as a duplicate of that issue.
--
nosy: +r.david.murray
stage: ->
Changes by R. David Murray :
--
nosy: +kushal.das
___
Python tracker
<http://bugs.python.org/issue21600>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by R. David Murray :
--
resolution: -> rejected
stage: -> resolved
status: open -> closed
___
Python tracker
<http://bugs.python.org/issue21637>
___
___
R. David Murray added the comment:
And our policy is that enhancements can only go in the next release.
We cannot change the default behavior in maintenance releases for backward
compatibility reasons, and we cannot provide for a requested change in behavior
without introducing an API
Changes by R. David Murray :
--
nosy: +brett.cannon, eric.snow
___
Python tracker
<http://bugs.python.org/issue21614>
___
___
Python-bugs-list mailing list
Unsub
R. David Murray added the comment:
No, there is no requirement that attachment names be unique, and in fact no
requirement that attachments (inline attachments, which is mostly what we are
dealing with for 'related') have names at all. I have seen messages in the
wild that had mor
R. David Murray added the comment:
It should be possible to also change the tool to use OrderDicts, though.
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/issue21
R. David Murray added the comment:
Or does the data get decoded to a dict *before* it gets passed to the
object_hook? Probably, in which case nevermind...
--
___
Python tracker
<http://bugs.python.org/issue21
R. David Murray added the comment:
Fixed. Thanks for the report.
--
nosy: +r.david.murray
resolution: -> fixed
stage: needs patch -> resolved
status: open -> closed
___
Python tracker
<http://bugs.python.or
R. David Murray added the comment:
Do either of you know what that warning is about? I'm getting it in some code
that I'm running successfully in both python2.7 and python3.4, and python3.4
doesn't give me a warning.
--
nosy:
R. David Murray added the comment:
Thanks.
--
nosy: +r.david.murray
resolution: -> fixed
stage: -> resolved
status: open -> closed
___
Python tracker
<http://bugs.python.or
R. David Murray added the comment:
I believe there are msg_NN files that have defects. I'd rather use one of
those in the exception test.
--
___
Python tracker
<http://bugs.python.org/is
R. David Murray added the comment:
I made some review comments.
Also, we need doc updates, including a what's new entry.
--
___
Python tracker
<http://bugs.python.org/is
R. David Murray added the comment:
Ah, you are right, I wasn't looking at the full context of the diff when I made
the comment about backward compatibility. So ignore that part :)
On the other hand, exposing perferred_auth on the class would be a simple API
for allowing auth extension (
R. David Murray added the comment:
Yes but the input is turned into a dict, and dicts do not preserve order.
Further, what is passed to the object_hook is already a dict, so the order is
already lost before object_hook is called.
Since the parser (or at least the Python version of the parser
R. David Murray added the comment:
Wait, I read the code wrong.
You can define object_pairs_hook, and use that to return an OrderedDict. So it
should be possible to do this without changing the json module itself. This is
actually documented as a place to use OrderedDict. Guess I should
Changes by R. David Murray :
--
resolution: -> out of date
stage: -> resolved
status: open -> closed
___
Python tracker
<http://bugs.python.or
Changes by R. David Murray :
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/issue21684>
___
___
Python-bugs-list mailing list
Unsubscribe:
R. David Murray added the comment:
No. The problem has nothing to do with the VS version.
--
___
Python tracker
<http://bugs.python.org/issue9012>
___
___
Pytho
R. David Murray added the comment:
On Linux I believe that what happens to the keyboard focus depends on the
window manager in use and how that window manager is configured to behave. For
instance, some window managers have a 'focus follows mouse' setting, but I
always hated that
Changes by R. David Murray :
--
nosy: +zach.ware
___
Python tracker
<http://bugs.python.org/issue21688>
___
___
Python-bugs-list mailing list
Unsubscribe:
R. David Murray added the comment:
But the actual call that you made in your example was some_method('foo', 'bar').
Given that we conventionally write unittest assertions with the actual result
first and the expected result second (assertEqual(actual, expected), it might
Changes by R. David Murray :
--
nosy: +lemburg
___
Python tracker
<http://bugs.python.org/issue21698>
___
___
Python-bugs-list mailing list
Unsubscribe:
R. David Murray added the comment:
This *can't* work on Linux (see issue 20622). I don't know if it is possible
to make it work on Windows, but I wonder: even if it is should we do so, since
the point of the launcher is to make shebang lines work on Windows more or less
how they
R. David Murray added the comment:
So if I'm understanding correctly the python update to the file happens
correctly in both cases, and the issue with the update not being immediately
visible is an issue on the OpenOffice side of things. So I'm closing this as a
3rd party bug
R. David Murray added the comment:
Well, now that I applied your patch it can be :) Thanks.
--
resolution: -> fixed
stage: needs patch -> resolved
status: open -> closed
versions: -Python 3.3
___
Python tracker
<http://bugs.python.or
R. David Murray added the comment:
When I run the modified test suite on a machine regrtest tells me that the test
modified the environment, specifically the asyncore.socket_map. Presumably
there is some missing cleanup logic.
--
___
Python
R. David Murray added the comment:
I'm hoping that with Argument Clinic we can do better, but I haven't played
with it so I'm not sure.
--
___
Python tracker
<http://bugs.pyt
R. David Murray added the comment:
Review comments added. Patch looks good after the doc fixes. We also need a
whatsnew entry.
--
___
Python tracker
<http://bugs.python.org/issue19
Changes by R. David Murray :
--
nosy: +r.david.murray
stage: -> test needed
___
Python tracker
<http://bugs.python.org/issue21705>
___
___
Python-bugs-list mai
R. David Murray added the comment:
Isn't this change going to cause unexpected data loss for (possibly mythical)
people depending on the existing behavior? At an absolute minimum it needs an
entry in the What's New porting section, but I'm wondering if a deprecation
R. David Murray added the comment:
Yeah, hopefully you are right. (I didn't mean to reopen the issue, by the way).
--
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
___
Python tracker
<http://bugs.pyth
R. David Murray added the comment:
It is true that the sqlite interface does not support WITH currently. It is an
interesting question whether or not we could change this as a bug fix or
not...I suppose it depends on whether or not it changes any behavior other than
making .description work
R. David Murray added the comment:
Thanks, Maciej.
I tweaked the patch a bit, you might want to take a look just for your own
information. Mostly I fixed the warning stuff, which I didn't explain very
well. The idea is that if the default is used (no value is specified), we want
the
New submission from R. David Murray:
I thought there was already an issue for this, but I can't find it. This is
part of this summer's GSOC work, and involves adding support for the SMTPUTF8
extension to smtpd.
--
components: email
messages: 220285
nosy: barry, jesste
Changes by R. David Murray :
--
hgrepos: +256
___
Python tracker
<http://bugs.python.org/issue21725>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by R. David Murray :
--
keywords: +patch
Added file: http://bugs.python.org/file35575/80ea1cdf2b23.diff
___
Python tracker
<http://bugs.python.org/issue21
R. David Murray added the comment:
Milan: your patch looks good for the most part. Now that I committed the
decode_data patch you should modify it so that SMTPUTF8 implies
decode_data=False (otherwise we *don't* have an 8-bit-clean channel). Please
either attach the modified patch he
Changes by R. David Murray :
--
hgrepos: -256
___
Python tracker
<http://bugs.python.org/issue21725>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by R. David Murray :
Removed file: http://bugs.python.org/file35575/80ea1cdf2b23.diff
___
Python tracker
<http://bugs.python.org/issue21725>
___
___
Python-bug
R. David Murray added the comment:
Thanks, Milan. I had to fix a couple things: you had left the "refactored"
methods on the SMTPDServerTest, and somehow your new TestFamilyDetection class
got indented under SMTPDServerTest in the new version of the patch. (I also
had to up
R. David Murray added the comment:
Thanks, Claudiu.
--
resolution: -> fixed
stage: -> resolved
status: open -> closed
___
Python tracker
<http://bugs.python.or
R. David Murray added the comment:
Hmm. Looks like the IPv6 support is making the FreeBSD and and OSX buildbots
unhappy :(.
--
status: closed -> open
___
Python tracker
<http://bugs.python.org/issu
R. David Murray added the comment:
OK, I think this is fixed.
--
status: open -> closed
___
Python tracker
<http://bugs.python.org/issue14758>
___
___
Python-
R. David Murray added the comment:
It is a clever idea, and might be worth considering, but it doesn't feel
natural to have to specify the attachments before the html. What I'd really
like is an API that hides the messy details of the RFC from the library user,
and I haven
R. David Murray added the comment:
Hmm. There's a conflict marker in that patch.
I *think* that if you do an 'hg pull --rebase' and then give your repository
URL to the tracker, the 'create patch' button will do the right thing. (I
tried it with the URL you sent m
R. David Murray added the comment:
See issue 7963 for a clue to why you get this message. That is, it is
object.__new__ that is getting called, not object.__init__, and __new__ methods
result in different error messages than __init__ methods. I don't know if
there is a practical way to
R. David Murray added the comment:
The code is mostly correct as it exists in the calendar module. You are
running into issue 10466. Per my comment in that issue, it may be possible to
put a workaround into the calendar module, but your suggestion isn't it, since
your code would leav
R. David Murray added the comment:
See issue 21731 for considering putting a workaround for this into the calendar
module (noted here because of msg122065).
--
___
Python tracker
<http://bugs.python.org/issue10
R. David Murray added the comment:
Oh, I see I'd already previously opened issue 10498 for that.
--
___
Python tracker
<http://bugs.python.org/issue10466>
___
___
R. David Murray added the comment:
I'm closing this in favor of issue 21731, which has a proposed (though I
believe incorrect) patch.
--
resolution: -> duplicate
stage: test needed -> resolved
status: open -> closed
superseder: -> Calendar Problem
R. David Murray added the comment:
In 3.x a list comprehension (like a generator expression in 2.x) *is* a
separate block:
>>> [x for x in range(3)]
[0, 1, 2]
>>> x
Traceback (most recent call last):
File "", line 1, in
NameError: name 'x' is not de
R. David Murray added the comment:
OK, I have no objection to leaving the 2.7 tutorial alone. It seems to me that
the 3.x tutorial should be fixed, though, because it currently says the
unrolled loop is equivalent, but it isn't. The fact that this applies to all
other comprehensio
R. David Murray added the comment:
For some reason the diff shown by the review link is very different from the
one show by the patch file itself. I'm not sure what is causing that, since
the diff appears to be in the correct hg format. I don't even know where
reitveld is getting
R. David Murray added the comment:
Correction on the XXX should we check this: I was thinking about the wrong
section of the code. But it is still 'no': by postel's law we should accept
dirty data. Currently the consumer of the library can then decide whether or
not to reject
R. David Murray added the comment:
Closing this in favor of issue 16512, which I will expand to include this case.
--
resolution: -> duplicate
stage: -> resolved
status: open -> closed
superseder: -> imghdr doesn't support jpegs wi
R. David Murray added the comment:
Issue 21230 reports a parallel problem with recognizing photoshop images.
We need a patch with tests covering the variant types we know about. I don't
have a strong opinion on the simple two byte test versus the more complex test
in msg220346, but foll
R. David Murray added the comment:
Sure. Would you like to propose a patch? It does seem that
NotImplementedError would be the most appropriate. It could give Christian's
reason why it is not implemented.
--
stage: patch review -> nee
R. David Murray added the comment:
Then don't use itertools for that case. itertools is designed for working with
*arbitrary* iterables, and arbitrary iterables are not seekable.
I'll leave it to Raymond to decide if it is worth making a special-case
optimization :)
-
R. David Murray added the comment:
You are missing an 's' after the parens. It should be: %(prog)s
--
nosy: +r.david.murray
resolution: -> not a bug
stage: -> resolved
status: open -> closed
type: -> behavior
___
R. David Murray added the comment:
I think there is no reason to impose the overhead of a sort unless the user
wants it...in which case they can sort it. I'm -1 on this change.
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.py
R. David Murray added the comment:
If I understand correct that patch was itself attempting to fix a regression ;)
--
___
Python tracker
<http://bugs.python.org/issue21
R. David Murray added the comment:
See also issue 17004 and issue 5950.
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/issue21751>
___
___
R. David Murray added the comment:
This should instead be an escape function parallel to the shlex.quote function
for unix. I was talking to someone on IRC the other day who had at least a
partial implementation, but I guess they haven't opened an issue for it. (At
least, I can'
R. David Murray added the comment:
This appears to be me to be obsolete, given that long messages are now the
default, and the message argument enhances the long message rather than
replacing it.
--
nosy: +r.david.murray
resolution: -> out of date
stage: -> resolved
status
R. David Murray added the comment:
Thanks, Caelyn. I used your patch but added a clause showing explicitly how do
the unicode conversion. I decided to not add that to the datetime, docs, since
they are already pretty clear.
--
nosy: +r.david.murray
resolution: -> fixed
stage: ne
R. David Murray added the comment:
Given the description it sounds likely that this is a tk bug.
--
assignee: -> ronaldoussoren
components: +Macintosh
nosy: +r.david.murray, ronaldoussoren
___
Python tracker
<http://bugs.python.org/issu
Changes by R. David Murray :
--
nosy: +ned.deily
___
Python tracker
<http://bugs.python.org/issue21757>
___
___
Python-bugs-list mailing list
Unsubscribe:
R. David Murray added the comment:
> My take is to avoid the problem entirely, and not inflict it to new users, by
> providing an option to start in autocommit mode and then create transactions
> only when you want them.
If this statement is accurate, the what you are proposing
R. David Murray added the comment:
I have to look at the implementation to remind myself how hard this would be to
implement. The goal was to leave Header a legacy API...if you need that level
of control, you use the old API. But I can see the functionality argument, and
Header *is* a
5101 - 5200 of 10554 matches
Mail list logo