R. David Murray added the comment:
When you say sometimes, do you mean randomly on the same schema, or do you mean
depending on the specific schema sometimes it doesn't work?
The code is the same in the other python versions, so I'm adding them as the
bug doubtless exists the
R. David Murray added the comment:
Please open a separate issue for your enhancement request in your second
message (assuming there isn't already one open). I'm not sure what your third
message is about, but it also sounds off topic for your original bug report.
For the FileCooki
Changes by R. David Murray :
--
nosy: +gps
___
Python tracker
<http://bugs.python.org/issue16946>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by R. David Murray :
--
resolution: -> fixed
stage: -> committed/rejected
status: open -> closed
___
Python tracker
<http://bugs.python.or
R. David Murray added the comment:
Please report pypi issues to the pypi bug tracker:
http://sourceforge.net/tracker/?group_id=66150&atid=513503
--
nosy: +r.david.murray
resolution: -> invalid
stage: -> committed/rejected
status: open
Changes by R. David Murray :
--
components: +email
nosy: +barry, r.david.murray
versions: +Python 3.3, Python 3.4
___
Python tracker
<http://bugs.python.org/issue16
R. David Murray added the comment:
Here is a revised patch. I am leaving out the changes relating to the
transaction manager. It turns out that the transaction manager doesn't do
anything useful even if isolation_level is not None. I'm going to open a new
issue to discuss the b
R. David Murray added the comment:
I misspoke, the transaction manager does do something useful in non-None
isolation level. I'm still going to open a bug about isolation_level None.
--
___
Python tracker
<http://bugs.python.org/i
New submission from R. David Murray:
Its operation is also not particularly intuitive if isolation_level is not
None, so its documentation needs some clarification.
Currently the transaction manager does nothing on enter, and does a commit or
rollback on exit, depending on whether or not
R. David Murray added the comment:
Opened issue 16958 for the transaction manager problem.
--
___
Python tracker
<http://bugs.python.org/issue8145>
___
___
Pytho
Changes by R. David Murray :
--
nosy: +nagylzs
___
Python tracker
<http://bugs.python.org/issue16958>
___
___
Python-bugs-list mailing list
Unsubscribe:
R. David Murray added the comment:
B, yes.
So you would view the connection context manager acting as an actual
transaction manager as a new feature? Would you be OK with adding that feature
to the existing context manager in 3.4 (since currently the context manager is
a noop in autocommit
R. David Murray added the comment:
It is valid, but it is not *useful* to have it in the bug tracker as an open
bug. All developers are aware that when they touch code for some other reason,
they can fix PEP8 errors at the same time. Having an open bug report for it
would just clutter the
R. David Murray added the comment:
Thanks for the suggestion and patch. I haven't reviewed it thoroughly yet, but
if you change _print_debug to be:
def _print_debug(*args):
then
print(datetime.datetime.now(), *args, file=stderr)
should do what you want for python3 (I don't
R. David Murray added the comment:
Er, that should have been (self, *args), but actually I'd recommend making it a
module function, not a method, in which case my signature would be correct :)
--
___
Python tracker
<http://bugs.py
R. David Murray added the comment:
Vis the discussion of x[:0] in the review. This kind of construct is only
unfamiliar because it is new in Python3, and there are not *that* many places
that you want to (and can) deal with both bytes and strings using the same
code. But when you can, it is
R. David Murray added the comment:
Since the line between a type error and a value error is fuzzy anyway, I'd be
in favor of maintaining the backward compatibility here. We don't consider
exception message content part of the API (though we do occasionally work to
preserve it wh
R. David Murray added the comment:
CPython only would not be appropriate, as it is not.
What I usually do in such cases is use AssertRaisesRegex looking for some
critical part of the message that represents the functionality we are looking
for rather than the exact text. In this case, it
R. David Murray added the comment:
The ideal is if someone says "looks good to me". The practical path is that if
you have addressed all the comments, and no one objects after a couple-three
days, you should feel free to commit (unless you feel like you want another
review, in whic
R. David Murray added the comment:
Heh. Nice find. I'm not sure how practical it is to fix, though. We don't
have any actual rules about what indicates a 'non-file-stand-in' for the
__file__ attribute, just a loose convention that it is an identifier in angle
brackets
R. David Murray added the comment:
Ideally there would be an unambiguous way to know if the object came from a
file or some other source (say, __file__ is None and another special attribute
gives the clue to the actual source), but that's not the way things work now,
and for bac
R. David Murray added the comment:
Hmm. A backward compatible fix would be to add an attribute that indicates
whether or not the __file__ attribute is supposed to be pointing to a real file.
--
___
Python tracker
<http://bugs.python.org/issue16
R. David Murray added the comment:
I wonder if importlib replicates this behavior, it may need fixing as well.
--
nosy: +brett.cannon, eric.snow, r.david.murray
___
Python tracker
<http://bugs.python.org/issue16
New submission from R. David Murray:
It has come to my attention that at least some mail agents apply postel's law
to addresses like the following:
From: "=?utf-8?Q?not_really_valid?="
Since encountering something that looks like an encoded word but that is not is
R. David Murray added the comment:
On linux/posix, the epoch is *defined* to be 1970, 1, 1 in UTC. Python just
uses whatever the OS defines the epoch to be, as far as I know.
--
___
Python tracker
<http://bugs.python.org/issue12
R. David Murray added the comment:
Wouldn't a non-greedy .* match the null string?
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/is
R. David Murray added the comment:
So, group() is returning the correct value, then.
--
resolution: -> invalid
stage: -> committed/rejected
status: open -> closed
___
Python tracker
<http://bugs.python.or
R. David Murray added the comment:
Christian, do you want to try to complete this before the 2.7.4 RC?
--
___
Python tracker
<http://bugs.python.org/issue16
R. David Murray added the comment:
What I think it is suppose to do (the user expects it to do) is find the
program that would be run if the command were typed at the command prompt.
rdmurray@hey:~>which python
/usr/bin/python
rdmurray@hey:~>export PATH=
rdmurray@hey:~>which python
p
R. David Murray added the comment:
I was speaking in general of 'which program would be executed if the command is
typed at the prompt' as being system dependent, which it demonstrably is since
the behavior on unix and windows differs with regards to the current
R. David Murray added the comment:
And no, what I wrote wasn't clear :)
--
___
Python tracker
<http://bugs.python.org/issue17012>
___
___
Python-bugs-list m
R. David Murray added the comment:
It's sort-of a bug, and sort-of not. getaddresses is expecting to parse an
already unfolded header, but the pre-3.3 email package does not unfold headers
automatically. See issue 11050 for more information.
--
resolution: -> duplica
Changes by R. David Murray :
--
components: +email
nosy: +barry, r.david.murray
___
Python tracker
<http://bugs.python.org/issue5430>
___
___
Python-bugs-list m
Changes by R. David Murray :
--
components: +email
nosy: +barry
___
Python tracker
<http://bugs.python.org/issue3461>
___
___
Python-bugs-list mailing list
Unsub
R. David Murray added the comment:
Can you post a small program that demonstrates the problem? I'm certainly not
seeing a problem just calling random.random() (and would be very surprised if I
did).
--
nosy: +r.david.murray
___
Python tr
R. David Murray added the comment:
That indeed looks likely. Fortunately there will be a new release of 2.7
including that fix soon.
Floris, do you have any way to test against 2.7 tip?
--
___
Python tracker
<http://bugs.python.org/issue17
R. David Murray added the comment:
hg pull http://hg.python.org/cpython
hg up 2.7
There are also git and bzr mirrors, but I don't know their urls or how up to
date they are.
We could also just close this as a dup if you are pretty sure its the same
problem (which it certainly sounds li
R. David Murray added the comment:
If you really want to freak out, try this:
>>> x = ([],)
>>> x[0] += [1]
Traceback (most recent call last):
File "", line 1, in
TypeError: 'tuple' object does not support item assignment
>>> x
([1],)
but to an
R. David Murray added the comment:
I agree that this is somewhat surprising, but it is working as intended.
a = b = c
is equivalent to
a = c
b = c
except that the RHS is evaluated only once, which can be important.
You were either expecting it to be equivalent to
b = c
a = c
R. David Murray added the comment:
I agree that this is not immediately intuitive.
What you need to know is that modules are part of the global state. When b
imports dbus.mainloop.glib, it affects the global state of the module dbus,
causing mainloop.glib to be defined when 'a' ref
R. David Murray added the comment:
Sure. It doesn't seem likely that I'll get back to it any time soon, and if I
do I can open a new issue.
--
stage: patch review -> committed/rejected
status: open -> closed
___
Pytho
R. David Murray added the comment:
Excellent. Thanks for testing. And thanks for pointing out the duplicate,
Peter.
--
assignee: ronaldoussoren ->
resolution: -> duplicate
stage: -> committed/rejected
status: open -> closed
superseder: -> Value returned by random.
R. David Murray added the comment:
Once upon a time (two years ago?) we fixed the tests so that they ran
successfully (skipped when appropriate) with -OO set, which omits docstrings.
We were checking for the optimization level (sys.flags.optimize) then. It
seems like it would make more
R. David Murray added the comment:
I don't think it should be .. note, but otherwise it looks fine to me.
--
___
Python tracker
<http://bugs.python.org/is
R. David Murray added the comment:
Stefan: as Serhiy pointed out, the two parameters control different things.
While it may be true that it is *likely* that someone would use both if they
use one, it is not guaranteed. I think it is better to keep them separate,
since while they are related
R. David Murray added the comment:
Is VS2012 actually involved in anything here? Does something get compiled when
you install rhodecode?
Since it is a third party package, it may be that no one here will volunteer to
reproduce this (though it is possible). If you can isolate the failure
R. David Murray added the comment:
I think the support functions just ignore errors. Isn't this going to continue
to leave garbage on the buildbot filesystem without fixing the underlying
problem? I wonder if this is a variation on the usual Windows access errors,
in which case perhaps
R. David Murray added the comment:
Ah, excellent. I had missed that change.
This looks good then. Hopefully it will work :)
--
___
Python tracker
<http://bugs.python.org/issue17
R. David Murray added the comment:
Thanks for your suggestion, but...
The example currently in the docs is exactly how we do deferred translation in
the project I am currently working on. Your example is much more complex, and
I don't see the benefit of it.
Specifically, using the ex
R. David Murray added the comment:
Sorry, I didn't mean "computed at runtime", I meant defined in code where the _
call is *executed* at runtime, rather than at import time.
--
___
Python tracker
<http://bugs.pyt
R. David Murray added the comment:
I prefer to have some of them be links and some of them be code markup. That
is, I think there is value in having some of them be links. As Georg said, the
devguide rule is more about it not being *necessary* to waste time marking them
*all* up as
R. David Murray added the comment:
Note, by the way, that I apply the same rule to most link markup. If I refer
to, say, a module name in a paragraph or set of related paragraphs multiple
times, I will typically only mark up the first occurrence as a :mod: link.
It's not a hard and
R. David Murray added the comment:
I would be very careful trying to reason by analogy there. ==, is, and
javascripts === are rather different in detail, from what I understand. Nor do
I see what javascript has to do with this issue :)
As far as the remaining documentation issue here, IMO
R. David Murray added the comment:
Indeed. The whole point of that section is to explain how the library can
refrain from spewing unwanted logging *if the application doesn't care about
logging*. If the application does care (has configured logging), it would be
wrong to block the lo
R. David Murray added the comment:
True. I disagree with the existing language, as I've indicated, but I'll leave
it up to Georg as doc master.
--
___
Python tracker
<http://bugs.python.o
Changes by R. David Murray :
--
nosy: +barry
___
Python tracker
<http://bugs.python.org/issue17078>
___
___
Python-bugs-list mailing list
Unsubscribe:
R. David Murray added the comment:
If you are reading in binary mode, then all readline does is get you the next
\n terminated chunk of data, which is a convenience in some circumstances. You
have to do all the newline handling yourself. Otherwise it isn't a binary read.
I think the &
R. David Murray added the comment:
As noted in the documentation, the csv module in 2.7 does not handle unicode.
You'll have to switch to python3 if you want unicode support in csv.
--
nosy: +r.david.murray
resolution: -> invalid
stage: -> committed/rejected
status: ope
R. David Murray added the comment:
Well, it is consistent with plain reasoning if you remember that (a) python is
a dynamic language and (b) python assignments do not return values (this is a
core principle in the language design), which means that (c) the chained
assignment form is a
R. David Murray added the comment:
Anything we do here is a new feature.
I have no objection to adding features in this area myself, but I will note
that I was shot down for proposing (in another issue) that the newline
attribute for text files be allowed to be an arbitrary string
R. David Murray added the comment:
Well, it's a feature by our policy, since it currently works as documented.
Probably the first thing would be to get the opinion of someone who works on
the IO module, so I've nosied Antoine. Note that this was obviously a
conscious design decis
R. David Murray added the comment:
Please see issue issue 1044. I have no opinion here, I just remembered that
this had been discussed before.
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/issue17
R. David Murray added the comment:
Please provide a complete example of the failures. Your report doesn't
currently provide enough information to reproduce the reported issue.
If the reported error message is accurate, it looks at first glance like the
error message at least could use
New submission from R. David Murray:
I came across this by making a mistake, but it shouldn't crash:
rdmurray@hey:~/python/p32>touch temp
rdmurray@hey:~/python/p32>./python
Python 3.2.3+ (3.2:e6952acd5a55+, Feb 2 2013, 15:04:21)
[GCC 4.6.3] on linux2
Type "help", &quo
R. David Murray added the comment:
It might not crash on a debug build. I haven't tried that.
--
___
Python tracker
<http://bugs.python.org/issue17106>
___
___
R. David Murray added the comment:
I mean, non-debug build.
--
___
Python tracker
<http://bugs.python.org/issue17106>
___
___
Python-bugs-list mailing list
Unsub
R. David Murray added the comment:
OK, this happens in debug mode in 3.2.3, so it is not a regression. Still
something to be looked in to, since that assert presumably has a purpose.
--
keywords: -3.2regression
priority: release blocker -> normal
type: crash -> behavior
ve
Changes by R. David Murray :
--
title: Crash in IO reading text file as binary via email library -> assertion
error in IO reading text file as binary
___
Python tracker
<http://bugs.python.org/issu
R. David Murray added the comment:
This is behavior has been true since packages were introduced, and is not going
to change. However, I agree that it could be better documented.
In Python3 something that needs to do dynamic module discovery can use
importlib to be sure of using the same
R. David Murray added the comment:
It was mostly the language reference I was thinking of, since that's where I
think one would naturally go to find out about unexpected behavior of the
import statement, but a note in the tutorial is probably not a bad idea. I'm
not sure if this ri
R. David Murray added the comment:
Ah, yes.
To clarify for Shai, by the way, the reason this stuff can't change (and the
reason there is a new step 3 instead of changing the whole algorithm to be
something more sensible) is because of the requirement of maintaining backward
compatib
R. David Murray added the comment:
Yes. Imagine you have a deployed application, and there happens to be an xx.py
file that is masked by a package in it. You upgrade from pythonX.Y.Z to
X.Y.Z+1, and your application is suddenly throwing an error. Yes it is easy to
fix, but we prefer not to
R. David Murray added the comment:
Armin is talking about the docstring, not the docs. That is, what you get if
you do help(x.acquire), where x is a Lock object, at the Python prompt.
--
nosy: +r.david.murray
___
Python tracker
<h
Changes by R. David Murray :
--
versions: +Python 3.3, Python 3.4 -Python 3.5
___
Python tracker
<http://bugs.python.org/issue17091>
___
___
Python-bugs-list m
R. David Murray added the comment:
Thanks, Ian.
--
resolution: -> fixed
stage: -> committed/rejected
status: open -> closed
versions: +Python 3.2
___
Python tracker
<http://bugs.python.or
R. David Murray added the comment:
The docs could certainly be more explicit...currently they state that tokenize
is *detecting* the encoding of the file, which *implies* but does not make
explicit that the input must be binary, not text.
The doc problem will get fixed as part of the fix to
R. David Murray added the comment:
The autoloading error will be fixed in 2.7.4 (due out Real Soon Now, but not
immediately).
I've nosied the author, Dave Malcolm, to address the other issues.
--
nosy: +dmalcolm, r.david.murray
___
Python tr
R. David Murray added the comment:
Fixed, thanks. There are some other issues with folding values consisting of
only blanks, but I'll deal with that in the context of other issues. With this
fix the new folding algorithm works at least as well as the old folding
algorithm on blank v
R. David Murray added the comment:
Fixed. I'm glad you caught this before the final release of 3.2. This is a
bit of an embarrassing bug :(.
--
resolution: -> fixed
stage: -> committed/rejected
status: open -> closed
type
R. David Murray added the comment:
I think Victor meant "not" instead of "now".
It doesn't only occur when your run particular programs, it occurs whenever the
microseconds are zero. It is possible that your particular combination of
programs produces a timing p
R. David Murray added the comment:
No, it is not "it's not broke because there's a workaround", it is not broken
because it is *working as designed*.
The str of any object in python is intended to be a convenient representation
of that object. Note that this applies
R. David Murray added the comment:
Good catch, thanks. A copy and paste error, I suppose.
--
nosy: +r.david.murray
resolution: -> fixed
stage: -> committed/rejected
status: open -> closed
type: enhancement -> behavior
versions: +Python 2.7, Python 3.2
R. David Murray added the comment:
No. As I said, datetime.now() returns a *datetime object*. Formatting only
becomes involved when you format an object, and that applies to *any* datetime
object, and is correctly documented in __str__ + isoformat.
Please do not reopen the issue again
R. David Murray added the comment:
You are correct. Effectively every class has an __str__, and that is what gets
called when you print something without specifying any other formatting. (I
say effectively, because if there is no __str__ the __repr__ gets used, which
every class *does* have
R. David Murray added the comment:
Looking at the documentation, it is clear that (a) what you are trying to do is
documented as being correct and (b) it worked in Python2, making this a
regression.
I've attached a patch to fix this, which also probably fixes some bugs with
BytesGene
R. David Murray added the comment:
Updated patch after review by Ezio and Serhiy.
--
Added file: http://bugs.python.org/file28990/encode_noop.patch
___
Python tracker
<http://bugs.python.org/issue16
R. David Murray added the comment:
While related, that is a different bug, so I'd rather open a new issue for it.
--
___
Python tracker
<http://bugs.python.org/is
Changes by R. David Murray :
--
status: closed -> open
___
Python tracker
<http://bugs.python.org/issue6972>
___
___
Python-bugs-list mailing list
Unsubscri
R. David Murray added the comment:
They should be capitalized and marked up as code if they refer to the objects.
If they refer only to (to use bad english) the truthiness or falsiness of the
value in question, then they should be lower case and not marked up as code.
Quickly scanning the
R. David Murray added the comment:
It passes on all our buildbots, and for me locally. Is it possible there is a
proxy server between you and python.org that is changing the url returned?
--
nosy: +r.david.murray
___
Python tracker
<h
R. David Murray added the comment:
I think only if you want to. As far as we are concerned the test is correct
and passing. (And this kind of thing is the reason that that test set is only
run when -uall is specified.)
I'm going to close the issue. If you do investigate, and feel
R. David Murray added the comment:
It has to be that way to preserve backward compatibility, since IIUC before the
PEP there was no such thing as "an initless package", it was just a directory
that was ignored by import.
--
___
Pyth
New submission from R. David Murray:
Reported by Serhiy in issue 16564:
>>> import io, email
>>> bytesdata = b'\xfa\xfb\xfc\xfd\xfe\xff'
>>> msg = email.mime.application.MIMEApplication(bytesdata,
>>> _encoder=encod
R. David Murray added the comment:
I've opened issue 17171 for the similar encode7or8bit problem.
--
resolution: -> fixed
stage: patch review -> committed/rejected
status: open -> closed
___
Python tracker
<http://bugs.pyth
R. David Murray added the comment:
Thanks, Berker.
--
nosy: +r.david.murray
resolution: -> fixed
stage: -> committed/rejected
status: open -> closed
type: -> behavior
___
Python tracker
<http://bugs.python
R. David Murray added the comment:
I don't really have strong feelings about this, but I will just note as a data
point that I implemented parameterized tests for the email package, and have no
interest myself in subtests. This is for exactly the collection time vs
runtime reason
R. David Murray added the comment:
Thanks, Jeremy.
--
resolution: -> fixed
stage: -> committed/rejected
status: open -> closed
type: -> behavior
versions: +Python 2.7, Python 3.2 -Python 3.5
___
Python tracker
<http://bugs.python
R. David Murray added the comment:
Lacking a reproducer, there's not much we can do here, so closing.
--
resolution: -> works for me
stage: test needed -> committed/rejected
status: open -> closed
___
Python tracker
<http:
Changes by R. David Murray :
--
type: -> behavior
___
Python tracker
<http://bugs.python.org/issue17171>
___
___
Python-bugs-list mailing list
Unsubscri
R. David Murray added the comment:
Since this was straightforwardly similar to the issue 16564 fix I didn't bother
with a review. The 2.7 commit is backporting the behavior-confirming test,
just for thoroughness.
--
resolution: -> fixed
stage: needs patch -> committ
5401 - 5500 of 10554 matches
Mail list logo
