R. David Murray added the comment:
I don't think that's true, though. "file like" pretty much means "has the file
attributes that I actually use". That is, it is context dependent (duck
typing).
I'm also not sure I see the point in the change. It is inher
R. David Murray added the comment:
It's Michael's solution that is under consideration, and I guess no one has
felt strongly enough about having it to write a patch. So this issue stays in
limbo until someone does.
--
___
Python trac
R. David Murray added the comment:
Thanks Caelyn. This patch also needs a doc patch and a whatsnew entry in order
to be complete. It's not obvious to me where the relevant documentation is,
though, so perhaps we instead have missing documentation that should be
addressed in a separate
R. David Murray added the comment:
Since there is no guarantee anyone is going to tackle the job of reviewing all
the changes for whatsnew entries, I prefer that we get in the habit of creating
the entries as we go along.
As for the versionchanged...if you can find where include is documented
R. David Murray added the comment:
Yes, I think that is appropriate. Note that you also get RFC822 parsing for
datetime via email.util.parsedate_to_datetime.
(I'm not sure why the OP thought that using the email utilities to parse
email-standard dates was "not [a] ver
Changes by R. David Murray :
--
resolution: -> duplicate
stage: test needed -> resolved
___
Python tracker
<http://bugs.python.org/issue5207>
___
___
Pyth
R. David Murray added the comment:
+1 from me (after verification), which should probably go without saying since
I'm the one that started this ball rolling by making regrtest work with
unittest discovery :)
I think the potential disruption to existing patches and any forward porting
i
R. David Murray added the comment:
Supporting ISO 8601 is quite different from supporting RFC2822 dates, as far as
I can see, and the latter clearly belongs in the email library (especially
considering that RFC2822 parsing must follow Postel's Law and accept "dirty"
data).
R. David Murray added the comment:
The statement is poorly worded. The id() is the *input* to the hash function
used to compute the default __hash__. This is a CPython implementation detail,
though, so perhaps all mention of it should indeed be dropped.
--
nosy: +r.david.murray
R. David Murray added the comment:
Yes, I should have been clearer. By "poorly worded" I meant "id is involved,
but the sentence does not correctly describe *how* id is involved". That is,
the sentence is wrong as written.
The implementation is the same in both Python2
R. David Murray added the comment:
Nikolaus: while I agree that Raymond's comments were a bit strongly worded, it
doesn't read to me as if the thread you link to is on point for this issue.
The thread was focused on a *specific* question, that of calling close twice.
The questi
R. David Murray added the comment:
It doesn't matter that it can't happen in CPython. The idea is that IronPython
should be able to copy as much of the stdlib as possible without having to
change it.
That said, I'm not going to object if people decide this is in some sense a
R. David Murray added the comment:
It doesn't use logging because (I think) logging didn't exist when it was
implemented. Whether or not we want to change that is a more complicated
question, I think. Probably we don't, for backward compat
Changes by R. David Murray :
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/issue15025>
___
___
Python-bugs-list mailing list
Unsubscribe:
R. David Murray added the comment:
Review comments added.
--
___
Python tracker
<http://bugs.python.org/issue21725>
___
___
Python-bugs-list mailing list
Unsub
Changes by R. David Murray :
--
nosy: +barry, eli.bendersky, ethan.furman, orsenthil
___
Python tracker
<http://bugs.python.org/issue21793>
___
___
Python-bug
R. David Murray added the comment:
Well, but we think it's pretty clear. The glossary entry says file object
interfaces are defined by the classes in the io module. As do the io module
docs. Perhaps the first sentence of the io docs could be modified to
strengthen that (but it already
R. David Murray added the comment:
Re-reading my last paragraph, I see that I'm pretty much agreeing with you. So
the contention is more that we don't think your suggested patch is necessary.
Especially since, unlike your patch wording says, in fact most of the methods
*are* impl
R. David Murray added the comment:
I believe Antoine was suggesting that you suggest wording that would make it
clear (rather than implied) that close was idempotent, but "This method has no
effect if the file is already closed" seems pretty unambiguous to me, so I
don't real
R. David Murray added the comment:
I would expect addition to return PosixPath('/tmp/some_base/_name.dat'), (ie:
path.join).
--
nosy: +pitrou, r.david.murray
___
Python tracker
<http://bugs.python.o
R. David Murray added the comment:
Issue 19645 is an alternative way to solve the problem of calling methods on
the mixin that "don't exist", and has other benefits.
--
___
Python tracker
<http://bugs.pyt
R. David Murray added the comment:
os.execlp *wraps* the interface of the same name in the platform C library. On
Windows, that is execlp in the msvcrt[*]. On Linux, it is usually the execlp
in glibc.
[*] 'crt' stands for
R. David Murray added the comment:
According to a review done at the PyCon 2014 sprints, comment and blank line
preservation has not yet been implemented.
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/issue1410
R. David Murray added the comment:
I don't understand your use case. As a user I would expect a switch to either
set the value to true or to false, not to toggle it based on some default that
might be changed in a configuration file.
But, your method of accomplishing your goal looks fi
Changes by R. David Murray :
--
nosy: +vinay.sajip
___
Python tracker
<http://bugs.python.org/issue21807>
___
___
Python-bugs-list mailing list
Unsubscribe:
R. David Murray added the comment:
I agree with Haypo, because if he isn't interested in doing it, it is unlikely
anyone else will find the problem tractable :) Certainly not anyone else on
the core team. But, the danger of breaking things in 2.7 is the clincher.
--
R. David Murray added the comment:
Is the purpose of this issue just informational, then? It would be better to
have a listing of active platform forks somewhere in the docs, I think,
assuming we don't already.
--
nosy: +r.david.murray
___
P
R. David Murray added the comment:
If it really wasn't a bug, we couldn't backport it. However, we generally
treat RFC non-compliance issues as bugs unless fixing them is disruptive (and
this one isn't because I took care to maintain backward compatibility in the
original patc
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:
This is no longer an issue in Python3; there utimes is used if it is available
(if utimensat is not).
Since this doesn't affect the platforms actually supported by python2.7, I'm
closing this as out of date.
--
nosy: +r.david.murray
Changes by R. David Murray :
--
nosy: +lukasz.langa
___
Python tracker
<http://bugs.python.org/issue16374>
___
___
Python-bugs-list mailing list
Unsubscribe:
R. David Murray added the comment:
It seems to me that if as Terry suggests both the English and the translation
are output then most of Ezio's concerns would be addressed. Maybe we could
even start a new trend in error message internationalization :)
An important question that needs
R. David Murray added the comment:
I didn't look at the patch...I assumed we were only talking about the message.
There seems little point in translating any other part of the traceback, other
than maybe the boilerplate between traceback sections. My thought was that the
translation
R. David Murray added the comment:
Ezio: ah. I guess I don't read the Description column of attachments, only the
filename :)
--
___
Python tracker
<http://bugs.python.org/is
R. David Murray added the comment:
OK, so this is an enhancement to specifically allow preservation of "unsafe"
permissions?
Adding the nosy list from issue 3394.
--
nosy: +cbrannon, pitrou, swarren
type: behavior -> enhancement
versions:
R. David Murray added the comment:
Can you post the error, please?
--
nosy: +r.david.murray
type: crash -> behavior
___
Python tracker
<http://bugs.python.org/issu
R. David Murray added the comment:
Is it possible you installed 3.3 differently? For example 3.2 and 2.7
installed for all users and 3.3 for just you, or vice versa?
>From the looks of the traceback there really is a permission problem with the
>file, since it is failing on a norma
Changes by R. David Murray :
___
Python tracker
<http://bugs.python.org/issue16145>
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/o
R. David Murray added the comment:
I don't know. I was able to remove him. (I have javascript turned off, don't
know if that makes any difference).
--
___
Python tracker
<http://bugs.python.o
R. David Murray added the comment:
Doesn't look like it.
--
stage: -> committed/rejected
status: open -> closed
___
Python tracker
<http://bugs.python.
R. David Murray added the comment:
The reason for our "no new features" policy is that if a program works with
version x.y, it should work for all x versions (modulo failing on an earlier
version because of a bug...and conversely if it works on x.y, it should work on
all later ver
R. David Murray added the comment:
It is a nice suggestion, but it is also probably a non-trivial change to the
parser. If you want to try coming up with a patch we would consider it, but I
suspect there is a limit to how much complexity we'd be willing to add to the
parser code for
R. David Murray added the comment:
Ah. Well, we prefer to err on the side of strictness for backward
compatibility, so I think we should treat this as an enhancement, then.
--
___
Python tracker
<http://bugs.python.org/issue1207
Changes by R. David Murray :
--
resolution: -> duplicate
stage: -> committed/rejected
status: open -> closed
superseder: -> urllib/httplib header capitalization
___
Python tracker
<http://bugs.python
R. David Murray added the comment:
Well, I run linux, not Windows. I haven't even looked at your code, frankly,
since it is a zip file and includes third party stuff. Maybe a windows dev
will find time to look at it.
--
___
Python tracker
R. David Murray added the comment:
The "system default shell" (which should always be a /bin/sh workalike, I
think) should always be the default. Any other shell should be something that
has to be specified explicitly. At least, that's the way most posix programs
work, I t
R. David Murray added the comment:
I think it would not be ok to import shutil in os, so I'm glad there is an
alternative.
--
___
Python tracker
<http://bugs.python.org/is
R. David Murray added the comment:
It doesn't matter whether it is a bug or not (though it is not in the situation
I described). The point is that a working program would stop working. That is
the kind of breakage our backward compatibility policy is designed to protect
ag
R. David Murray added the comment:
This behavior is inherited from optparse. I think it is more-or-less
intentional, and in any case it is of long enough standing that I don't think
we can change it. We documented it for optparse in another issue, but I don't
think we made the cor
R. David Murray added the comment:
We aren't particularly interested in helping people make their files slightly
harder to reverse engineer, either, so I don't think that is a good enough
reason for accepting this. There might be other reasons that are good enough,
but I don'
R. David Murray added the comment:
> If the encryption is so horrible why is there any support (with bad
> performance) at all in Python?
I would say it there so that people can use python to "decrypt" an "encrypted"
zip archive they have been sent that was genera
Changes by R. David Murray :
--
stage: -> committed/rejected
status: open -> closed
___
Python tracker
<http://bugs.python.org/issue16413>
___
___
Pyth
R. David Murray added the comment:
eventlet is not a part of the Python standard library. Please report this bug
to the project's bug tracker.
--
nosy: +r.david.murray
resolution: -> invalid
stage: -> committed/rejected
status: ope
R. David Murray added the comment:
You did request a tuple:
r = a - q * b,
That is equivalent to
r = (a - q * b,)
which is a single element tuple.
I had to put in some print statements in your loop to find that, it wasn't
obvious. This is perhaps a disadvantage of Python&#x
R. David Murray added the comment:
I don't think choices is a good choice there (pardon the pun). You really want
a custom type. I'm inclined to think that that applies to any 'choices' value
that is 'too large' for the help display. Part of the point of choice
R. David Murray added the comment:
There is an example in the test suite somewhere. Probably in the distutils
tests. Search for xxmodule...but you'll need to create your own source. I'd
see if you can write it out from the test rather than checking in another data
file, but a da
R. David Murray added the comment:
Sorry, didn't mean to change the component back.
--
components: +Interpreter Core -Extension Modules
type: behavior -> enhancement
versions: +Python 3.4 -Python 3.5
___
Python tracker
<http://bugs
R. David Murray added the comment:
It looks like there is a patch, so a patch review would be the next step (as
indicated by the stage, not that we always remember to update that...)
Reading the issue carefully and making sure that all the concerns are addressed
is also required. A comitter
R. David Murray added the comment:
Given the backward compatibility concerns, and the fact that brace expansion
and wildcard expansion are conceptually separate operations, perhaps what we
should have a is a glob.expand_braces (or some such name) function? (Note: I
haven't looked at wh
R. David Murray added the comment:
This is a question more suited to be asked on python-list or python-tutor,
rather than a bug report.
I'll give you a clue while I'm closing the issue: in the font snippt you
reference the font attribute when your module is imported. In the
R. David Murray added the comment:
I agree with Antoine. It seems to me that it is very important to the
semantics of rollover that the rename be atomic, even if we ignore the issue of
existing other readers. If it were not atomic, you might end up with lost log
messages. So I don't
R. David Murray added the comment:
It is not so much that it isn't a priority, as that no one has suggested a
working fix that is suitable for 2.7. Do you have a suggestion?
--
resolution: fixed ->
___
Python tracker
<http://bugs
New submission from R. David Murray:
Consider this code snippet, simplified from a real application:
def display(self, *columns)
getter = attrgetter(*columns)
toprint = [[str(x) for x in getter(row)] for row in self._rows]
This works great...as long as there are two or more columns to
R. David Murray added the comment:
Are you asking to have seen_greeting passed in the server.process_message call?
That is reasonable.
--
components: +email
nosy: +barry, r.david.murray
versions: +Python 2.6 -Python 2.7, Python 3.1, Python 3.2, Python 3.3
R. David Murray added the comment:
On the other hand, it would also be backward incompatible.
Can anyone think of a backward compatible way to provide this info? Maybe we
could use the new signature object support.
--
___
Python tracker
<h
Changes by R. David Murray :
--
versions: +Python 3.4 -Python 2.6
___
Python tracker
<http://bugs.python.org/issue16462>
___
___
Python-bugs-list mailin
R. David Murray added the comment:
Given Nick's point about itemgetter, I agree this isn't worth doing. I
wouldn't want the signatures of attrgetter and itemgetter to no longer be
parallel.
Min isn't a problem, by the way, since it accepts an iterator a
R. David Murray added the comment:
The file certainly exists, since Python requires it to run. It sounds like
cx_Freeze just doesn't support Python3.3 yet. I don't see that this is a
Python bug.
--
nosy: +r.david.murray
___
Python trac
R. David Murray added the comment:
I agree with Chris that using the repr in the general case would be a
regression in usability for the end user (and certainly not suitable for a
maintenance release).
Here is some brainstorming:
We could "special case" this via duck typing. If
R. David Murray added the comment:
I think I can answer your last question. There are two quopri algorithms, one
where spaces are allowed (message body) and one where they aren't (email
headers).
For the rest, I'd have to take a closer look than I have time for
R. David Murray added the comment:
Not necessarily. The fact that there is nothing to load doesn't mean it isn't
the right loader if there *was* something to load. But I'll leave it to the
import experts to say what the expected behavior is. I'll admit that I can
R. David Murray added the comment:
Any chance you could reduce this to a simpler test case? It may be a while
before anyone gets around to analyzing your complete example.
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.
R. David Murray added the comment:
If it "got it" from dBasis[163] via item assignment (say gList1[i1][1] =
dBasis[163]), then yes, Python remembers that. Names just hold pointers to
objects, so after that assignment gList1[i1][1] points to the same object as
dBasis[163] does
R. David Murray added the comment:
Thanks for the work, but we don't generally make bulk changes like this. It
generates churn in the codebase, and has the risk of inadvertently changing the
meaning of the tests, to little actual benefit. Instead we modernize tests
when we touch the
R. David Murray added the comment:
Yes, so I suppose you could add a footnote that says "using a three way merge
tool generally makes this step unnecessary".
Is there a bug report for this on the mercurial tracker? If so we could link
to the
New submission from R. David Murray:
When debugging using tests or doing test driven development, I find it very
useful to have the test run exit immediately on the first failure. Doctest
currently has a feature to suppress all output after the first failure, but not
to exit on the first
New submission from R. David Murray:
It looks like the use of the 'args' formal parameter was cut and pasted from
the methodcaller docs, when it is not appropriate for itemgetter and attrgetter.
http://docs.python.org/3/library/operator.html#operator.attrgetter
--
assi
R. David Murray added the comment:
Looks great, I didn't think any changes were needed. Thanks a bunch, Daniel.
--
resolution: -> fixed
stage: needs patch -> committed/rejected
status: open -> closed
___
Python tracker
<http:
R. David Murray added the comment:
This is intentional. Only 2.7, 3.3, and 3.4 auto-update now that 3.3 is out.
There will be a final rebuild of the 3.2 docs when 3.2 final is released.
--
nosy: +r.david.murray
resolution: -> invalid
stage: -> committed/rejected
status
R. David Murray added the comment:
I don't know. If it is would be in wherever "documenting Python" is these
days. The policy is that only the versions in active maintenance are
automatically rebuilt. 3.2 is technically no longer in maintenance, it's just
that there are
R. David Murray added the comment:
Agree with the rejection. os.system is intended to be a minimal wrapper around
the system call, as are most things in the os module, and as such mirroring the
behavior of the system call (by returning -1) is less surprising than raising
an exception, even
R. David Murray added the comment:
This is probably related to #1692335. It looks like that fix was not
backported. Can you test if your example works now in 3.3?
--
nosy: +r.david.murray, sbt
___
Python tracker
<http://bugs.python.org/issue16
R. David Murray added the comment:
Yes, the way BytesGenerator works is basically a hack to get the email package
itself working. Use cases outside the email package were not really considered
in the (short) timeframe during which it was implemented.
The longer term plan calls for redoing
R. David Murray added the comment:
Hmm. Let me rephrase that. *Internally* it doesn't support bytes payloads, it
"encodes" bytes payloads as surrogateescaped ascii, as you have oserved. Which
is why this is on the borderline, and could possibly be considered a bug fix,
R. David Murray added the comment:
"Code smell" and "Easily fixable on their side" are not an arguments that apply
here. We have a strong backward compatibility policy that strives not to break
working code in bug fix releases. And yes, this means that there are sometime
R. David Murray added the comment:
Yes, I think the risk of breaking doctests (and breaking them in a very
mysterious way...trailing spaces) is high enough that we shouldn't backport the
fix, unfortunately.
--
___
Python tracker
R. David Murray added the comment:
Since it looks like that is your buildbot, can you do some command line testing
to see what is going wrong with the gdb invocation? I'm wondering if perhaps
this feature was backported as a security patch, so that the gdb version check
is an insuffi
R. David Murray added the comment:
Thanks for the patch.
Could you either include a test or post code that demonstrates the problem,
please?
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/issue16
R. David Murray added the comment:
Is your error report the fact that the name 'tuple' appears in the error
message instead of 'c'? That does seem sub-optimal. It may not be easy to
improve, though.
--
nosy: +r.david.murray
priority: normal -> low
ti
R. David Murray added the comment:
In fact it has been changed. In Python3 you get:
>>> x = 0.88022393777095409
>>> x
0.8802239377709541
>>> str(x)
'0.8802239377709541'
Even in 2.7 you would get the above repr, not the one you showed. This is
becau
R. David Murray added the comment:
I have no idea what you are referring to by 'constructing str' :(
I thought at first it was your incorrect tuple call in the init that was the
issue, but that didn't look right, and after reproducing it and playing with it
for a bit I figured
R. David Murray added the comment:
I don't see the bug here.
Your for loop calls wrap. Wrap calls emptygen. Emptygen raises a
StopIteration exception. That exception is of course propagated upward (it
isn't caught by wrap), and the loop stops.
--
nosy: +r.david.murray
R. David Murray added the comment:
That's why I suggested a glossary entry. The relevant function description
*does* contain the phrase "floating point", so a glossary link there would be
reasonably natural.
--
___
Python
R. David Murray added the comment:
I followed the link, but it took me to a login/signup form, so it wasn't very
informative.
--
___
Python tracker
<http://bugs.python.org/is
R. David Murray added the comment:
The only way I was able to replicate that result was by removing the entire
try/except block, including the yield. In that case, wrap is no longer a
generator, so the exception is raised before you enter the for loop
R. David Murray added the comment:
It is both documented
(http://docs.python.org/dev/library/argparse.html#argument-abbreviations) and
an important feature.
I thought there was an enhancement request in this tracker for making the
behavior optional, but I couldn't find it when I looke
Changes by R. David Murray :
--
nosy: +Michael.Edwards
___
Python tracker
<http://bugs.python.org/issue14910>
___
___
Python-bugs-list mailing list
Unsubscribe:
R. David Murray added the comment:
It is indeed. And it even has a patch. Don't know how I missed it.
--
resolution: -> duplicate
stage: needs patch -> committed/rejected
superseder: -> argparse: disable abbreviation
___
Python
R. David Murray added the comment:
I wonder if both bugs are symptoms of an underlying bug: if you call 'iter'
twice on a tarfile, are the iterators independent? Is that even a sensible
thing to be able to do?
--
nosy: +r.david.murray
R. David Murray added the comment:
I will note that on unix the user is also free to update the machine's mime
types registry (that's more than half the point of the mimetypes module).
Usually this is only done by installed software...as I believe is the case on
Windows as well.
5201 - 5300 of 10554 matches
Mail list logo
