R. David Murray added the comment:
email in python3 doesn't necessarily work with binary payloads. (Obviously
here you've found the opposite problem, but it is in methods that aren't used
by the package itself.) There aren't any tests of binary payloads in the test
sui
Changes by R. David Murray :
--
keywords: +needs review
stage: -> patch review
type: -> enhancement
___
Python tracker
<http://bugs.python.org/i
R. David Murray added the comment:
Thanks for the report and patch. However, in general we prefer not to mask
exceptions (doing that can hide bugs in programs). It would probably be
reasonable to fix this in pydoc, however.
Alternatively there might be a specific exception or set of
R. David Murray added the comment:
After this commit the buildbots are dying randomly with segfaults.
--
nosy: +r.david.murray
priority: normal -> release blocker
status: closed -> open
___
Python tracker
<http://bugs.python.org/i
R. David Murray added the comment:
Looking at the traceback and your code, configparser is calling 'get',
expecting to call its own get method (that takes a 'raw' keyword), but instead
is calling the get on your subclass, which doesn't take a 'raw' keyword.
R. David Murray added the comment:
Michael, I thought you might be interested in this one since it looks like it
might involve inspect executing code unexpectedly, and I know you worked on
ways of not doing that...
--
nosy: +michael.foord
Changes by R. David Murray :
--
resolution: -> invalid
stage: -> committed/rejected
status: open -> closed
___
Python tracker
<http://bugs.python.or
R. David Murray added the comment:
You might want to take a look at the Decimal module.
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/issue14
R. David Murray added the comment:
This appears to be causing buildbot failures:
http://www.python.org/dev/buildbot/all/builders/x86%20debian%20parallel%203.x/builds/4077
http://www.python.org/dev/buildbot/all/builders/AMD64%20Gentoo%20Wide%203.x/builds/3520
--
keywords: +buildbot
R. David Murray added the comment:
Great. I'm going to close the issue, but it's only "for now": if you get a
good response and a design agreement on python-ideas please reopen the issue.
Of course, we'd need a patch, too; and I believe there would need to be
R. David Murray added the comment:
Pretty close. I'd do the check for us_ascii first, and only do the encode
test/switch to utf-8 if that's the charset. The reason is that that if a
charset has been specified, we don't waste time doing an unnecessary encoding
(and the asci
R. David Murray added the comment:
That looks good.
--
stage: test needed -> commit review
___
Python tracker
<http://bugs.python.org/issue14380>
___
___
Py
R. David Murray added the comment:
You are theoretically right about not posting trivial patches, but as you can
see, sometimes even a trivial patch elicits unexpected insights. So I like to
always post my patches, even the seemingly trivial ones. Then if I don't get
any respons
Changes by R. David Murray :
--
assignee: -> r.david.murray
___
Python tracker
<http://bugs.python.org/issue12553>
___
___
Python-bugs-list mailing list
Un
Changes by R. David Murray :
--
assignee: -> r.david.murray
___
Python tracker
<http://bugs.python.org/issue7304>
___
___
Python-bugs-list mailing list
Un
R. David Murray added the comment:
In Python2 the fix would be to use charset unknown-8bit instead of us-ascii.
In Python3 this actually puts unicode in the message body. There we should
default to utf-8, but this requires a more extensive change than the Python2
change, and probably should
R. David Murray added the comment:
See also issue 7304. It was niggling at the back of my brain, and I finally
managed to dig it up. Fixing that is much more complex than fixing this
(because set_charset is a *very* strange method), so I committed this patch in
case we don't manage t
R. David Murray added the comment:
Better, but not stable:
http://www.python.org/dev/buildbot/all/builders/AMD64%20OpenIndiana%203.2/builds/984/steps/test/logs/stdio
http://www.python.org/dev/buildbot/all/builders/x86%20OpenIndiana%203.2/builds/998/steps/test/logs/stdio
R. David Murray added the comment:
Please, give it a try. But also be prepared for it being harder than it looks;
the problem is that there may be very limited knowledge available where the
error is generated. (I don't know; I haven't looked at the code and am not
likely to..
R. David Murray added the comment:
@telmich: I think you will have more success at getting what you want if you
work with us rather than being confrontational. Respect that we have reasons
for doing things a certain way (and not because we are stupid), and we will
respect your perspective
R. David Murray added the comment:
I believe it was actually Guido who suggested exposing dict_proxy, in response
to Victor (but independent of Victor's needs, if I understood the message
correctly).
It has always seemed odd to me ("always" referring my time working with
Pyt
R. David Murray added the comment:
I'm marking this as easy hoping someone in the mentoring group will pick it up
and take a look. The relevant code is in Python, and I'm guessing there is
some logic bug when only the comment is set (and nothing is added to the
zipfile), but
R. David Murray added the comment:
There is no sftp module in the standard library. Presumably you are talking
about a 3rd party product and should report the bug to its developers.
If you are trying instead to report a bug in the logging module, please reopen
the issue if you can provide a
R. David Murray added the comment:
OK, so whatever else is true, it seems like there isn't anything for the python
core dev team to do here. Any action would take place at the www.python.org
level, and this bug tracker isn't where such changes are tracked, so I'm
cl
Changes by R. David Murray :
--
type: -> enhancement
___
Python tracker
<http://bugs.python.org/issue14379>
___
___
Python-bugs-list mailing list
Unsubscri
Changes by R. David Murray :
--
nosy: -smccardell
___
Python tracker
<http://bugs.python.org/issue786827>
___
___
Python-bugs-list mailing list
Unsubscribe:
R. David Murray added the comment:
The bug tracker is not a good place to get programming help. Please try the
python-tutors list, or the general python-list (see mail.python.org for a list
of mailing lists). There will be people on one of those lists with time to
help you out
R. David Murray added the comment:
Somebody (Raymond?) is going to go through and edit for style and consistency
before the release. But I applied your tweak anyway.
--
nosy: +r.david.murray
resolution: -> fixed
stage: -> committed/rejected
status: open -&g
R. David Murray added the comment:
Looks like someone else noticed the problem, but did not notice that there was
an existing issue with a patch :(.
Sorry about that, Mark. Thanks very much for working on this, and I'm very
sorry it got lost. Hopefully Eli will review your patch and s
R. David Murray added the comment:
> Limited by what?
The alphabet.
I suppose we could use a -- option, but somebody would have to add support for
those.
--
___
Python tracker
<http://bugs.python.org/issu
R. David Murray added the comment:
I must admit to being concerned by the possible impact of this change as well.
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/issue14
R. David Murray added the comment:
LOG_SYSLOG and LOG_UUCP have been present in Python for a *long* time (since
1998 at least).
The other two are not. What fallbacks should be used if they don't exist?
(I believe you meant 'facilities', rather than 'priorities'.)
-
R. David Murray added the comment:
Looking at this again, as_string defaults to maxheaderlen=0, which means no
wrapping. In Python 3.2 you can pass it a maxheaderlen of 78 to get the
correct behavior for passing the message to smtp.
--
resolution: -> invalid
stage: -> com
R. David Murray added the comment:
Hmm. When I did the same (changed to b'...') and ran it, I got an archive
test.zip. When I then opened that archive using ZipFile, its comment attribute
was b''. Thus I concluded that the bug exists in Python3. I don't remembe
Changes by R. David Murray :
--
stage: -> committed/rejected
status: open -> closed
___
Python tracker
<http://bugs.python.org/issue5301>
___
___
Pyth
Changes by R. David Murray :
--
resolution: -> duplicate
status: open -> closed
superseder: -> test_httpservers on Debian Testing
___
Python tracker
<http://bugs.python.o
R. David Murray added the comment:
That's probably reasonable (we have precedents for that in other modules),
except that that's not how the older possibly-not-there constants work. For
backward compatibility reasons we can't change the older constants, but I don't
see
R. David Murray added the comment:
Frederico: thanks for the patch. Do you want to do the doc patches as well?
--
___
Python tracker
<http://bugs.python.org/issue14
R. David Murray added the comment:
Thanks for the patch.
The advantage of the more complicated way being that you get an immediate
TypeError instead of a delayed one? Is there any other advantage? (That's
probably enough reason, though :)
Now we just need a unit test for
R. David Murray added the comment:
Close. We either need to mention that LOG_AUTHPRIV is only defined if the
platform defines it, or we need to change the implementation so that it is
always defined (by mapping it to some other facility if it doesn't exist). I'm
of mixed mind abo
R. David Murray added the comment:
Got you. We'll definitely go with the more complete fix, then.
--
___
Python tracker
<http://bugs.python.org/is
R. David Murray added the comment:
I believe there is an example in the packaging unit tests of building an
extension module in a test (but I'm not 100% sure).
Also, the fact that the test will deadlock if it fails is not a deal breaker:
the test should pass normally, and if it fail
New submission from R. David Murray :
Currently the prototype uses timeout=socket._GLOBAL_DEFAULT_TIMEOUT, and the
docs give the prototype as:
urlopen(url, data=None[, timeout], *, cafile=None, capath=None)
which is unlike most other Python function prototypes in the docs, and makes no
R. David Murray added the comment:
Thinking about this some more, I think that AUTHPRIV is special. You don't
want to inadvertently log AUTHPRIV stuff to some other facility. So I think
the code patch is good, and we should add a note to the docs that AUTHPRIV may
not exist o
R. David Murray added the comment:
>From what I understand, that defeats the purpose of AUTHPRIV, which is to log
>messages that should be logged in a "safer" location than AUTH. That's why I
>said it was a special case. In other words, if an application is going
R. David Murray added the comment:
The tests don't seem to be included in the new patch. Also, you could
modernize the property definition (@property, @comment.setter).
--
___
Python tracker
<http://bugs.python.org/is
R. David Murray added the comment:
Thanks. Looks good to me. I'll give Senthil a little time to comment, in case
he disagrees with my proposal, before committing it.
We could conceivably apply this as a bug fix to 3.2, since I don't think there
is any backward compatibi
New submission from R. David Murray :
These appear from the source to be public methods (and I certainly want to be
able to use get_header), but they aren't documented.
--
assignee: docs@python
components: Documentation
messages: 156953
nosy: docs@python, r.david.murray
pri
R. David Murray added the comment:
Your presumption is probably correct, however if that is the premise of the
patch it is incorrect in detail, since we've already fixed test_queue
specifically to be runnable with -m unittest without adding a load_tests. I
haven't looked at
R. David Murray added the comment:
The test_main functions can be converted to use unittest discovery, though.
That's what I did for test_email.
--
___
Python tracker
<http://bugs.python.org/is
R. David Murray added the comment:
Right. What I meant to say was "test_main can be converted to use normal
unittest test loading". test_email is not an example of that, since it does
use test discovery, but is a good example of a test collection that works with
both regrtest an
Changes by R. David Murray :
--
keywords: +needs review
nosy: +belopolsky
stage: -> patch review
versions: -Python 2.6, Python 2.7, Python 3.1, Python 3.2, Python 3.4
___
Python tracker
<http://bugs.python.org/issu
R. David Murray added the comment:
To make this a little clearer, here's an even simpler example:
>>> import os
>>> os.fdopen(0)
<_io.TextIOWrapper name=0 mode='r' encoding='UTF-8'>
>>> 1
__main__:1: ResourceWarning: unclosed file
R. David Murray added the comment:
Hmm. And D isn't how you shut down the interpreter on Windows, is it? So
maybe there is a Windows-specific bug here after all. Or do you get that same
dialog if you do the Windows equivalent of D in a shell window (is that
different from a CMD windo
R. David Murray added the comment:
It sounds like we just need to fix the TestCase inheritance, like we did in
test_queue.
We should also look more carefully at the threading setup/cleanup. At some
point I think we changed the best-practice idiom to be independent of regrtest,
but we
R. David Murray added the comment:
OK, let's reopen this for someone to investigate that Windows crash.
--
resolution: invalid ->
stage: committed/rejected -> needs patch
status: closed -> open
title: Python 3 interpreter crash with memoryview and os.fdopen -> Pyth
Changes by R. David Murray :
--
title: Python 3 interpreter crash on windows when stdin closed -> Python 3
interpreter crash on windows when stdin closed in Python shell
___
Python tracker
<http://bugs.python.org/issu
R. David Murray added the comment:
It should be easy enough to patch this to use
http://docs.python.org/./tutorial
I think that is probably a good idea, but the doc folks should sign off on it.
--
keywords: +easy
nosy: +r.david.murray
title: Tutorial link in "help()"
R. David Murray added the comment:
Thanks for the patch.
However, the RFC is one thing, but what happens in the real world? Cookies are
very messy in the real world, and we cannot just assume that the RFC version
works.
--
nosy: +r.david.murray
R. David Murray added the comment:
Thanks, Federico, and welcome to the ACKS file.
It looks like you are planning to contribute more, so if you haven't already
done so could you please submit a contributor agreement?
http://www.python.org/psf/contrib/contrib-form/
--
resol
Changes by R. David Murray :
--
nosy: +vinay.sajip
___
Python tracker
<http://bugs.python.org/issue14436>
___
___
Python-bugs-list mailing list
Unsubscribe:
R. David Murray added the comment:
Not particularly elegant? Why not? I find marking tests that should be
executed by having them (and only them) inherit from TestCase to fit my sense
of what is Pythonic, while having a hidden please-ignore-me attribute doesn&#
R. David Murray added the comment:
Hmm. OK, I guess we can just disagree on what looks straightforward, and since
you are the maintainer of unittest you win :) But unless somebody pronounces,
I'll probably keep using the mixin pattern for my own mo
R. David Murray added the comment:
I guess I'm not really done talking about this, though my bow to you as
maintainer still stands.
The mixin tests *can't* be run in isolation, that's the whole point. Otherwise
you could just let unittest run them, and wouldn't need
R. David Murray added the comment:
The convention in the stdlib is to name the mixin classes TestXXXBase.
Granted, a lot of those inherit from TestCase. I have no objection to calling
them Mixin instead, I'm just pointing out that there is an existing convention.
(As an aside, when I
R. David Murray added the comment:
We pretty much follow the posix standard on strftime. I doubt that we would
introduce non-standard specifiers. Are there any in widespread use for your
use case?
--
nosy: +belopolsky, r.david.murray
___
Python
R. David Murray added the comment:
I'm asking if there are specific % codes commonly used for this case. (Even if
there are there is no guarantee we are going to add them, but it makes it
possible to make a case for it.)
--
___
Python tr
R. David Murray added the comment:
It turns out that there is standard way to do this (well, a de-facto standard,
anyway). glibc (and apparently others) support 'modifiers', of which the '-'
modifier will suppress 0 padding. Furthermore, since we pass the format stri
R. David Murray added the comment:
Thanks Ross. I don't think this is worth a news item, even though the bug was
shipped in an alpha. If someone disagrees please add one.
--
stage: needs patch -> committed/rejected
status: open -> closed
type:
R. David Murray added the comment:
Ah, woops, I *thought* I'd looked at the diff, but obviously I didn't. Sigh.
--
___
Python tracker
<http://bugs.python.o
R. David Murray added the comment:
I think there may even be an issue for that, but with the currently broken
issue search I'm not sure. Issue 3173 *might* be what I'm thinking of (thanks,
google).
And yes, the fact that stuff like this is not cross-platform is why it isn't
R. David Murray added the comment:
Raymond is suggesting removal in 3.4, and given that we are doing it I don't
see any reason to wait for 3.5, either, so you probably want to update the
warning messages to say 3.4 instead of 3.5. Otherwise it looks good to me.
Ezio suggested adding a
Changes by R. David Murray :
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/issue1>
___
___
Python-bugs-list mailing list
Unsubscribe:
R. David Murray added the comment:
At the very least the docs should be clarified to say that you have to call
shutdown from a separate thread. (The one example of using it does do that.)
I don't have a strong opinion about the proposed new method, not having used
socketserver excep
R. David Murray added the comment:
This is a duplicate of issue 12291. 3.1 is in security-fix only mode.
--
nosy: +r.david.murray
resolution: -> duplicate
stage: -> committed/rejected
status: open -> closed
superseder: -> file written using marshal in 3.2 can be read
R. David Murray added the comment:
If I understand correctly, this would be a backward incompatible change, so I
doubt it will be accepted. Maybe there's some other way to achieve the same
end?
--
nosy: +bethard, r.david.murray
___
Python tr
Changes by R. David Murray :
--
nosy: +vinay.sajip
___
Python tracker
<http://bugs.python.org/issue14452>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by R. David Murray :
--
versions: -Python 2.6, Python 3.1, Python 3.4
___
Python tracker
<http://bugs.python.org/issue14452>
___
___
Python-bugs-list m
R. David Murray added the comment:
The current behavior is how we want the functions to work. If you want to
debate the design, the best forum would probably be python-ideas.
--
nosy: +r.david.murray
resolution: -> rejected
stage: -> committed/rejected
status: open -&g
R. David Murray added the comment:
It is, yes.
Can you do some debugging and see why it is failing? It should be simple
enough to add a print to see what magic number Python is seeing.
--
nosy: +r.david.murray
___
Python tracker
<h
R. David Murray added the comment:
Oh, actually...are you sure you are running 3.2.3 against the 3.2.3 stdlib? It
looks like you might be running against the Apple default installed library,
but I don't know enough about OSX to be
R. David Murray added the comment:
Oh, I meant sticking a print statement into the stdlib code.
But I really think your problem is that you aren't running the 3.2.3 stdlib
code.
Try opening up the file
/Library/Frameworks/Python.framework/Versions/3.2/lib/python3.2/dbm/__init__.py
in
R. David Murray added the comment:
Well, that's the correct line. So if that is what is in your
/Library/Frameworks/Python.framework/Versions/3.2/lib/python3.2/dbm/__init__.py,
then there is a problem. If so, please put the line:
print(magic)
just before that if statement, and l
Changes by R. David Murray :
--
type: -> enhancement
___
Python tracker
<http://bugs.python.org/issue14446>
___
___
Python-bugs-list mailing list
Unsubscri
R. David Murray added the comment:
Looks like this should be closed rejected?
--
nosy: +r.david.murray
type: -> enhancement
___
Python tracker
<http://bugs.python.org/issu
Changes by R. David Murray :
--
type: -> enhancement
___
Python tracker
<http://bugs.python.org/issue14386>
___
___
Python-bugs-list mailing list
Unsubscri
R. David Murray added the comment:
Duplicate of issue 11231.
--
nosy: +r.david.murray
resolution: -> duplicate
stage: -> committed/rejected
status: open -> closed
superseder: -> bytes() constructor is not correctly documented
___
Py
Changes by R. David Murray :
--
resolution: -> fixed
stage: patch review -> committed/rejected
status: open -> closed
___
Python tracker
<http://bugs.python.or
R. David Murray added the comment:
Thanks for the patch. Could you upload it as a context diff?
--
nosy: +r.david.murray
stage: -> patch review
versions: +Python 3.3 -Python 2.7
___
Python tracker
<http://bugs.python.org/issu
R. David Murray added the comment:
Hmm. Apparently what I meant was -u instead of -c (unified diff). I just use
the 'hg diff' command myself, which does the right thing :) Of course, to do
that you need to have a checkout. (We can probably use the co
R. David Murray added the comment:
Ned: that shouldn't prevent whichdb from figuring out the type of the db file,
though, if I understand correctly.
Niklas: that's unexpected, so I suspect something is not right about how you
inserted the print. You did say you were a Python newbie
R. David Murray added the comment:
It sounds like manolo69 is just confused about what the append operation
returns (which is None). Since this is a carefully considered part of the
design of Python (operations that mutate objects rather than creating a new
object return None), I'm cl
Changes by R. David Murray :
--
nosy: +brian.curtin
___
Python tracker
<http://bugs.python.org/issue14458>
___
___
Python-bugs-list mailing list
Unsubscribe:
R. David Murray added the comment:
Fixed. Thanks for the report, Bill.
--
resolution: -> fixed
stage: -> committed/rejected
status: open -> closed
___
Python tracker
<http://bugs.python.or
R. David Murray added the comment:
Thanks, Nick, this is much better than speculation.
--
___
Python tracker
<http://bugs.python.org/issue14417>
___
___
Pytho
R. David Murray added the comment:
Yes, Nick's library looks good, but that should be a separate issue, it isn't
really relevant to this one.
--
___
Python tracker
<http://bugs.python.
R. David Murray added the comment:
Which just goes to show that using Popen correctly is not obvious, I suppose.
Given that adding these errors *would* break backward compatibility, there
would have to be a deprecation if it was done.
Personally I don't see the point in adding new
R. David Murray added the comment:
Antoine: I don't think the point of this code is to come up with a unit (or
other) test for the behavior, but to try to determine empirically whether or
not this error is likely to be an issue in naive production code (whether it is
existing 3.x co
Changes by R. David Murray :
--
type: -> enhancement
___
Python tracker
<http://bugs.python.org/issue14465>
___
___
Python-bugs-list mailing list
Unsubscri
R. David Murray added the comment:
The FAQ link (and removing the new style class link, but I think there is
already an issue for that) is the only one I see that should be pointing to 3.x
that isn't.
python.org/doc and docs.python.org is intentionally the 2.7 docs for now. We
ha
2501 - 2600 of 10554 matches
Mail list logo
