R. David Murray added the comment:
Oh, I misread your code.
The code I'm working on uses the lock to serialize several different functions,
and your decorator wouldn't work for that.
--
___
Python tracker
<http://bugs.python.o
Changes by R. David Murray :
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/issue15635>
___
___
Python-bugs-list mailing list
Unsubscribe:
R. David Murray added the comment:
If I remember correctly it existed in one of the versions (python vs C) but not
in both. Or, it existed but wasn't actually respected by one of the versions.
--
nosy: +pitrou, r.david.murray
___
Python tr
R. David Murray added the comment:
English-wise I would drop the "Also".
You say "differs from the one supplied", but given the rest of the text I would
expect that it is really "differs from the supplied mode masked with the
current umask, on systems where the mode
R. David Murray added the comment:
@Michael: Thanks for working on this. I don't see a patch attached to the
issue, though.
--
___
Python tracker
<http://bugs.python.org/i
R. David Murray added the comment:
Thanks for working on this.
I see nothing wrong with using 'universal newlines mode' as the term, which
would simplify the markup.
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.o
R. David Murray added the comment:
Thanks!
--
resolution: -> fixed
stage: test needed -> committed/rejected
status: open -> closed
___
Python tracker
<http://bugs.python.o
R. David Murray added the comment:
Benjamin confirms a regression in his patch, and the other patch was not
intended for CPython. So I'm closing this issue.
--
nosy: +r.david.murray
stage: patch review -> committed/rejected
status: open -
Changes by R. David Murray :
--
resolution: -> duplicate
stage: needs patch -> committed/rejected
status: open -> closed
superseder: -> Windows installer should add Python and Scripts directories to
the PATH environment variable
___
Py
Changes by R. David Murray :
--
nosy: +benjamin.peterson
___
Python tracker
<http://bugs.python.org/issue15645>
___
___
Python-bugs-list mailing list
Unsubscribe:
R. David Murray added the comment:
Chris isn't suggesting changing the behavior, just the error message. I agree
with his change for exactly the reason you say: currently doctest doesn't
complain if a module does have docstrings but none of those docstrings are
tests. So a module
R. David Murray added the comment:
That's a good question. Perhaps you could argue for it as a bug fix since it
doesn't seem to be documented either way...except for the 'exclude_empty'
argument of testmod. If testmod throws an error when there are no docstrings
inst
R. David Murray added the comment:
Yeah, we might as well be consistent, though it's not a big deal either way.
I'd prefer that as a separate patch.
Any interest in backporting this to 2.7? Being so close to final release on
3.2 I think we can skip 3.2, unless you feel lik
R. David Murray added the comment:
I believe this is a duplicate of issue 4625.
--
nosy: +r.david.murray
resolution: -> duplicate
stage: -> committed/rejected
status: open -> closed
superseder: -> IDLE won't open anymore, .idlerc unaccessible
type:
R. David Murray added the comment:
The example you uploaded doesn't call multiprocessing, yet the traceback you
show does. Can you provide more details on what you are actually doing? Note
that if you are importing a module that does a fork when it is imported, you
are doing something
R. David Murray added the comment:
Thanks, Chris.
--
nosy: +r.david.murray
resolution: -> fixed
stage: -> committed/rejected
status: open -> closed
___
Python tracker
<http://bugs.python.or
R. David Murray added the comment:
No it isn't. There's some issue about a 'U' parameter somewhere that is being
deprecated, but that has nothing to do with this issue.
--
___
Python tracker
<http://bug
R. David Murray added the comment:
So this should be closed as a duplicate of issue 12669?
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/issue15
R. David Murray added the comment:
Thanks Chris.
--
resolution: -> fixed
stage: patch review -> committed/rejected
status: open -> closed
type: -> enhancement
___
Python tracker
<http://bugs.python
R. David Murray added the comment:
This is fixed in more recent versions of Python (2.7, 3.2+).
--
nosy: +r.david.murray
resolution: -> out of date
stage: -> committed/rejected
status: open -> closed
___
Python tracker
<http://bug
R. David Murray added the comment:
YAGNI, is what I think. Or if you do need it, put it in your application. (To
tell you the truth, it just looks confusing to me...it strikes me as too
magical.)
Regardless, this is more of a python-ideas kind of issue, so I suggest raising
it there if you
R. David Murray added the comment:
Thanks for your suggestion, even though I'm rejecting the suggestion as a bug
tracker issue. (I should have said that at the start of my answer.)
--
___
Python tracker
<http://bugs.python.org/is
R. David Murray added the comment:
I think it probably should be filed with sphinx instead, rather than also.
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/issue15
R. David Murray added the comment:
We do pin it, but we generally have no problem with upgrading. I think we
generally upgrade it exactly when there is a new Sphinx feature we want for our
docs :) We don't maintain local patches to Sphinx (though we do have code that
is specific to our
R. David Murray added the comment:
Well, I think it depends on what we consider the priority of the issue. So, I
personally would count this one as low, and would be happy that it gets fixed
whenever we happen to upgrade to a version of Sphinx that fixes it. If it is
an issue we consider
R. David Murray added the comment:
There are divided opinions about the advisability of backporting tests that are
not part of a bug fix. In this case, there is also the fact that it includes a
test that fails without a bug fix that was not backported
R. David Murray added the comment:
Chris, if Nick is too busy to reply right now and you want to move this along,
you could write some tests (not necessarily for inclusion in the test suite) to
confirm that the doc you are adding is correct. I don't know enough about
generators to co
R. David Murray added the comment:
We have plenty of "versionadded" and "versionchanged" tags for 3.1 in the docs.
We should add one for this as well to the 3.2 and 3.3 docs.
--
nosy: +r.david.murray
resolution: invalid ->
stage: committed/rejected ->
R. David Murray added the comment:
Because the spammer faked that address, presumably.
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/issue15
R. David Murray added the comment:
Thanks, Chris.
--
nosy: +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:
Confirmed that 2.7 raises the same errors (as I expected) using your test.
Thanks, Chris.
--
resolution: -> fixed
stage: patch review -> committed/rejected
status: open -> closed
___
Python track
Changes by R. David Murray :
--
resolution: -> fixed
stage: needs patch -> committed/rejected
status: open -> closed
___
Python tracker
<http://bugs.python.or
Changes by R. David Murray :
--
stage: -> committed/rejected
status: pending -> closed
___
Python tracker
<http://bugs.python.org/issue9271>
___
___
Pyth
R. David Murray added the comment:
I could be wrong, but it is hard for me to see how we could justify doing this
before python4, at this point in python3.
Adding a warning would be uncontroversial, though.
--
nosy: +r.david.murray
___
Python
R. David Murray added the comment:
This is much better. But let me try tuning the problem paragraph a bit, since
I'm a native English speaker:
If *exists_ok* is ``False`` (the default), an :exc:`OSError` is raised if
the target directory already exists. If *exists_ok* is ``True
R. David Murray added the comment:
Even if we write in chunks, if we are calling the OS write function and
O_APPEND is set, wouldn't be satisfying the condition? Or, rather, the OS
would be. That is, I don't really see a guarantee of an *atomic* write in the
quoted d
R. David Murray added the comment:
I've reviewed the patch and applied it.
2.7 doesn't support !a or 'ascii()', but I did backport the doc changes and the
reordering of the clauses in order to minimize code base drift.
Thanks, Francisco.
--
resolution: -> fix
Changes by R. David Murray :
--
superseder: -> subprocess.getoutput fails on win32
___
Python tracker
<http://bugs.python.org/issue5808>
___
___
Python-
R. David Murray added the comment:
Thanks, Mike.
--
resolution: -> fixed
stage: -> committed/rejected
status: open -> closed
versions: +Python 2.7, Python 3.2
___
Python tracker
<http://bugs.python.or
R. David Murray added the comment:
This is 3.3 only, as those tests and the function they test were only
introduced in 3.3.
--
components: +email
nosy: +barry, r.david.murray
versions: -Python 3.2
___
Python tracker
<http://bugs.python.
Changes by R. David Murray :
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/issue15753>
___
___
Python-bugs-list mailing list
Unsubscribe:
R. David Murray added the comment:
This is a new feature (ie: adding support for a new feature of sqlite).
Would you like to propose a patch?
--
nosy: +r.david.murray
stage: -> needs patch
type: behavior -> enhancement
versions: +Python 3.4 -Pyth
R. David Murray added the comment:
Having said this is a feature, since it would only affect the error message,
I'm actually open to it as a bug fix. It won't make it into 3.3.0 even if
someone proposes a patch, though, given that we are so late in the releas
Changes by R. David Murray :
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/issue10852>
___
___
Python-bugs-list mailing list
Unsubscribe:
R. David Murray added the comment:
Well, it would be patching the sqlite extension module. Not that that is much
different :)
Hopefully the current sqlite extension maintainer will think this is worthwhile
doing. Short of waiting for that, you could perhaps ask on the python-list
email
Changes by R. David Murray :
--
stage: -> committed/rejected
status: open -> closed
___
Python tracker
<http://bugs.python.org/issue15637>
___
___
Pyth
Changes by R. David Murray :
--
versions: +Python 3.4 -Python 3.2
___
Python tracker
<http://bugs.python.org/issue1207589>
___
___
Python-bugs-list mailin
R. David Murray added the comment:
Alexander, this slipped off my radar.
Some of the tests Brian added fail with the patch applied. I fixed most of
them by adding back the support for converting an aware datetime to an aware
localtime. The remaining two I believe are what you are fixing
R. David Murray added the comment:
So you are saying that if the current timezone is UTC, FreeBSD's mktime just
arbitrarily returns -1 for any time passed to it with the 'guess the DST flag'
value set for is_dst? And for is_dst set to 1 as well? This isn't mentioned
on
R. David Murray added the comment:
Heh, I was just copying the previous code, and didn't think about being able to
update it. Will make that change.
--
___
Python tracker
<http://bugs.python.org/iss
R. David Murray added the comment:
And my tests and code were wrong, and I was wrong about what you were trying to
fix. So since the other tests were passing before, presumably there is some
test that could be added to exercise the bug you were fixing. Do you remember
what that was
R. David Murray added the comment:
Doing non-ASCII email in python before 3.3 is a bit of a pain and not as well
documented as it should be. 3.3 will work more like you expect, if you use the
new provisional policies (which are intended to become standard in 3.4, after a
the bake-in period
R. David Murray added the comment:
It may or may not be too old to deserve comments, but it is too old to do
anything about it. This can't change for backward compatibility reasons, and
since optparse is deprecated in favor of argparse it isn't getting any new
features. We sti
R. David Murray added the comment:
I think restricting the test is fine. If we find a platform-specific bug on
another platform we can add a test specific to that platform when we fix the
bug.
Can you provide the test? I'm going to commit what I've got at this point to
make su
R. David Murray added the comment:
Leaving open until the test is committed.
--
assignee: r.david.murray ->
resolution: accepted -> fixed
___
Python tracker
<http://bugs.python.org/is
R. David Murray added the comment:
I thought that was an issue when I was looking at the code the other day, but I
didn't get around to testing it. Thanks for the report.
--
nosy: +orsenthil, pitrou, r.david.murray
stage: -> needs patch
__
R. David Murray added the comment:
Unfortunately I don't feel qualified to review the patch itself since I'm not a
windows user and don't currently even have a windows box to test on. Hopefully
one of the windows devs will take a look; the patch looks to be fairly
straightforw
R. David Murray added the comment:
Absent an argument in favor of reversion, I'm closing this.
--
stage: -> committed/rejected
status: open -> closed
___
Python tracker
<http://bugs.python.
R. David Murray added the comment:
It has been a while since I looked at the code, but if I remember correctly
there is a (somewhat non-obvious) mechanism for assigning priority to handlers,
so that you can control the order of application. If I'm right the insort is
about that priority
R. David Murray added the comment:
I didn't have anything specific in mind, just making a general comment about
the care that needs to be taken in crafting the fix.
--
___
Python tracker
<http://bugs.python.org/is
R. David Murray added the comment:
And in the meantime that RFC has been obsoleted by rfc 2392.
--
components: +email
stage: test needed -> needs patch
title: Support RFC 2111 in email package -> Support RFC 2392 in email package
___
Python t
R. David Murray added the comment:
moijes12: do you want to work on it? I haven't even read the RFC yet to find
out what "support it" means; too many other issues on my plate first.
--
___
Python tracker
<http://bugs.pyth
R. David Murray added the comment:
This is a duplicate of issue 7008. See also issue 6412, which offers some
small hope that some day there may be an algorithm that can fix this.
--
nosy: +r.david.murray
resolution: -> duplicate
stage: -> committed/rejected
status: open -&g
R. David Murray added the comment:
moijes12, thanks for the patch. Since this is a new feature we'll need to wait
until the 3.3 RC1 repo is branched before applying it.
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/is
R. David Murray added the comment:
Thanks, LittleQ. And Petri.
--
resolution: -> fixed
stage: patch review -> committed/rejected
status: open -> closed
___
Python tracker
<http://bugs.python.or
R. David Murray added the comment:
I'm guessing that 'batch file' version of this request is answered by the new
'py' launcher command in Python3, which can also be used with other versions of
Python. The obscurity of configuring things on Windows isn't directly
R. David Murray added the comment:
Personally I prefer to have the test case create the file(s) used in the test
dynamically, writing them to the temporary working directory. Since these are
Python modules, you could use the helpers from script_helpers for this.
Otherwise I think your patch
R. David Murray added the comment:
http://tools.ietf.org/html/rfc2387 has obsoleted 2112.
--
title: RFC 2112 in email package -> RFC 2387 in email package
versions: +Python 3.4 -Python 3.3
___
Python tracker
<http://bugs.python.org/issue
R. David Murray added the comment:
It looks to me like we (now, as of 67dc99a989cd) handle EINTR, so that the
suggested caveat is no longer true. Since the TTY example has also been
explained as correct, I'm going to close this. If I'm wrong about EINTR,
someone (Antoine
R. David Murray added the comment:
This looks like the answer to the cygwin question, assuming things haven't
changed:
http://cygwin.com/ml/cygwin-developers/2001-02/msg00106.html
Basically, it does the same thing as Python, except that a special return code
is reported by the ex
R. David Murray added the comment:
There is a proposed patch in issue 1065986 waiting for review.
--
nosy: +r.david.murray
resolution: -> duplicate
stage: -> committed/rejected
status: open -> closed
superseder: -> Fix pydoc crashing on unicode strings
type: crash
R. David Murray added the comment:
Does this have any relationship to issue 3394? From the discussion on that
issue it sounds like zipfile is doing things with external_attributes if it is
set. But I don't know much about zipfile internals.
--
nosy: +r.david.m
R. David Murray added the comment:
Could you explain the error you are seeing in more detail first? You are talk
about parsing and fixes here, but I'm not clear on what the actual bug is you
are reporting.
--
nosy: +r.david.murray
___
P
R. David Murray added the comment:
Why should it raise an error? The postel principle suggests that we should
treat it as equivalent to the second line.
--
___
Python tracker
<http://bugs.python.org/issue15
R. David Murray added the comment:
That doesn't appear to be true in 3.2. I happened to test this on
email.message.Message, and it also did not raise an error, but it defines an
__str__.
I suspect this is some oddball result of the coercion rules.
--
nosy: +r.david.m
R. David Murray added the comment:
Didn't get an error in 2.7, either, with Message().
--
___
Python tracker
<http://bugs.python.org/issue15801>
___
___
Pytho
R. David Murray added the comment:
Looks right to me on a quick scan, but I'm not familiar with that test.
--
nosy: +petri.lehtinen
___
Python tracker
<http://bugs.python.org/is
R. David Murray added the comment:
With your patch 5 applied, test_zipimport_support fails. I took a quick look
at this and it looks like it is because we've added a dependency on an external
data file to the test for DocTestSuite.
Note that with patch 4 applied, test_pyclbr fails...I
R. David Murray added the comment:
I think it works as it should (you shouldn't be asserting that a sequence and a
tuple are equal, after all). Once you fix your test, you'll get the pretty
print if there are still differences.
--
nosy: +michael.foord, r.da
R. David Murray added the comment:
That sounds like a bug.
--
title: assertSequenceEqual should be fired when comparing sequences ->
assertSequenceEqual should be fired when comparing sequence subclasses
___
Python tracker
<http://bugs.pyth
Changes by R. David Murray :
--
nosy: +lukasz.langa
___
Python tracker
<http://bugs.python.org/issue15803>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by R. David Murray :
--
stage: -> patch review
type: enhancement -> behavior
___
Python tracker
<http://bugs.python.org/issue15803>
___
___
Pyth
R. David Murray added the comment:
When you assign a value to param1 it becomes a local variable, thus the error.
You should ask for help on your scoping questions from the python-tutor list or
the general python-list.
--
nosy: +r.david.murray
resolution: -> invalid
st
R. David Murray added the comment:
Replacing __import__ is not supported.
That said, this is fixed in 3.3.
--
nosy: +r.david.murray
resolution: -> out of date
stage: -> committed/rejected
status: open -> closed
type: -> behavior
versions: +Python 3.3 -Python 2.7, Python
R. David Murray added the comment:
I'm inclined to think it isn't worth the effort, myself. I think a
"validating" client would be a valuable tool, but that that isn't what the
stdlib is focused on. But yes, let's hear Senthil's opinion.
(That said, I am
R. David Murray added the comment:
The problem is the timeformat. % codes are used to include data into the
strings, so if you want a literal % in the help string, you need to double it.
--
nosy: +r.david.murray
___
Python tracker
<h
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:
There is some extensive (and somewhat contentious) discussion of this on issue
2193. I myself am sympathetic to having a mode where parsing errors are
handled in a more convenient fashion, but it would pretty much have to be a new
feature.
--
nosy
R. David Murray added the comment:
I think the first step is probably to get consensus on whether this is
desirable or not. That might require a trip to python-idea, or it might not :)
As for the patch itself, you should definitely *not* include any changes other
than the ones you are
R. David Murray added the comment:
Actually, Senthil is right. What you want is the _replace method of namedtuple
to satisfy your use case.
--
resolution: -> works for me
stage: -> committed/rejected
status: open -> closed
___
Pytho
R. David Murray added the comment:
Not in this case. We are treating the URL as an immutable object, so the
Pythonic thing to do is create new object of the same type with the change
applied. Similar to "abcd".replace('a', 'z
R. David Murray added the comment:
Please see Issue 14502. The docs probably do need clarification, but it must
be done carefully.
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/issue15
R. David Murray added the comment:
It is possible this could be considered a feature rather than a bug :)
Let's see what Steven thinks.
--
nosy: +bethard, r.david.murray
versions: +Python 3.2, Python 3.3, Python 3.4
___
Python tracker
R. David Murray added the comment:
Sounds like a reasonable suggestion. However, the patch is not valid for 2.7,
since there exceptions can be old style classes.
--
nosy: +r.david.murray
stage: -> patch review
versions: -Python 2.6, Python 2.7, Python
R. David Murray added the comment:
I put some review comments in rietveld (you should have gotten an email).
--
___
Python tracker
<http://bugs.python.org/issue15
R. David Murray added the comment:
Is the :exc:`KeyboardInterrupt` line supposed to be in there?
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/issue15
R. David Murray added the comment:
Is test_bytes_glob_directory_with_trailing_slash unique to bytes, or should it
be added to the base class instead?
What would be useful as bytes-only tests, I think, would be tests of non-ascii
stuff.
Although that makes me wonder, do we test non-ascii
R. David Murray added the comment:
Uploading the new patch here is the correct procedure. It will automatically
be uploaded to rietveld as well.
If by "how" you mean how to submit a backport, just create a patch against 2.7
tip and upload it separately.
Revised patch
Changes by R. David Murray :
--
nosy: +michael.foord
___
Python tracker
<http://bugs.python.org/issue15836>
___
___
Python-bugs-list mailing list
Unsubscribe:
R. David Murray added the comment:
The patch seems to be missing.
The int=int is probably some sort of micro-optimization and perhaps should be
removed.
--
nosy: +r.david.murray, rhettinger
___
Python tracker
<http://bugs.python.org/issue15
4501 - 4600 of 10554 matches
Mail list logo