R. David Murray added the comment:
See also http://www.gratisoft.us/bugzilla/show_bug.cgi?id=464, which lists
versions. Sounds like the same bug Amaury linked to.
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/issue14
R. David Murray added the comment:
I'm going to close this. If it turns out not to be a bug in sudo, please
reopen.
--
resolution: -> invalid
stage: -> committed/rejected
status: open -> closed
___
Python tracker
<http:
Changes by R. David Murray :
--
nosy: +skrah
___
Python tracker
<http://bugs.python.org/issue14478>
___
___
Python-bugs-list mailing list
Unsubscribe:
R. David Murray added the comment:
One person that I helped at the PyCon sprints was using it, because the
devguide said to. But I think she was more confused by it than she would have
been by 'hg diff', at least to start out. Or maybe not...but I wasn't able to
help
R. David Murray added the comment:
LGTM.
--
___
Python tracker
<http://bugs.python.org/issue14466>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by R. David Murray :
--
nosy: +brian.curtin
stage: -> needs patch
type: behavior -> enhancement
___
Python tracker
<http://bugs.python.org/i
R. David Murray added the comment:
Thanks.
--
nosy: +r.david.murray
resolution: -> fixed
stage: -> committed/rejected
status: open -> closed
___
Python tracker
<http://bugs.python.or
R. David Murray added the comment:
Hmm. I would think it would be a good idea to have os.kill do posix emulation
where that makes sense, it makes cross-platform usage easier. That's what
'kill' with no signal does, right (kills the process, just like the posix
default)?
R. David Murray added the comment:
I would think that if Windows doesn't support a specific signal, os.kill should
raise a ValueError. But I'm an outsider here, I know nothing about how Windows
works for this except what I'm reading here.
To answer your question: there are
R. David Murray added the comment:
I made some time to work on this today. Attached is a new patch. I've
incorporated the tests from the existing patches (though I'm doing the
infrastructure a bit differently). PLAIN seems to be a specific case of the
general authenticate, so I
R. David Murray added the comment:
Well, it turns out that this design is intentional, because actually using the
global socket timeout is deprecated (see issue 2451). (That is, the non-None
default value of the timeout parameter is a backward compatibility hack.)
So I'm closing th
R. David Murray added the comment:
If gvfs is preferred, should its if block come second, or perhaps those two
should be an if/elif block?
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/issue14
R. David Murray added the comment:
This is only a problem in the 2.7 docs.
I tried adding a .. py:currentmodule:: builtins directive to the page, hoping
that would make all unqualified links local, but it didn't work. I think the
fix will require someone with more Sphinx-foo than I
R. David Murray added the comment:
Thanks for the patch.
Do you have an interest in trying your hand at writing a test for this to go
into Lib/test/test_tools.py?
--
nosy: +r.david.murray
stage: -> test needed
___
Python tracker
&l
Changes by R. David Murray :
--
stage: -> test needed
type: -> behavior
___
Python tracker
<http://bugs.python.org/issue14492>
___
___
Python-bugs-list
Changes by R. David Murray :
--
stage: -> test needed
___
Python tracker
<http://bugs.python.org/issue14491>
___
___
Python-bugs-list mailing list
Unsubscri
Changes by R. David Murray :
--
stage: -> patch review
versions: -Python 2.6, Python 3.1
___
Python tracker
<http://bugs.python.org/issue14494>
___
___
Py
R. David Murray added the comment:
Nevermind, it occurred to me that what we really need is a 'test_sundry' style
test for the tools. Here's a patch that adds that. I'll apply it after I fix
the other bugs it reveals (which include the other two you poin
R. David Murray added the comment:
OK, sounds fine. Shall we close this as fixed then?
--
___
Python tracker
<http://bugs.python.org/issue14493>
___
___
Pytho
R. David Murray added the comment:
Some of these at least are intentional. There are test files (especially in
2to3!) that use python2 syntax, and test files that have specially crated
syntax errors in them. Sphinx at one point was using Python2, I'm not sure if
it has been upgraded
R. David Murray added the comment:
Yes, that's why its status is still "open" :)
As far as I know no one is actively working on it (email issues are all
assigned to me so I can keep track of them, not because I'm actively working on
all of them).
At this point I haven&#x
R. David Murray added the comment:
Serhiy: I'm not sure what you are talking about. Does it relate to this
specific issue (abitype.py)?
--
___
Python tracker
<http://bugs.python.org/is
R. David Murray added the comment:
Thanks for the patch.
--
resolution: -> fixed
stage: test needed -> committed/rejected
___
Python tracker
<http://bugs.python.org/i
R. David Murray added the comment:
Fixed in 62dde5dd475e and 696cb524322a. Thanks for the patch.
--
resolution: -> fixed
stage: test needed -> committed/rejected
status: open -> closed
___
Python tracker
<http://bugs.python.or
Changes by R. David Murray :
--
status: open -> closed
___
Python tracker
<http://bugs.python.org/issue14491>
___
___
Python-bugs-list mailing list
Unsubscri
R. David Murray added the comment:
This one is not a syntax error, so the new 'sundry' tests don't catch it. Want
to write a test for this one?
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.pyt
R. David Murray added the comment:
Here's a run of your script against Python3.3
I see nothing on this list that is a problem (after the recent fixes in
Tools/scripts). The Doc stuff can be ignored, that's a Python2 based toolchain
checked out by the Doc 'make' file.
Changes by R. David Murray :
--
resolution: -> fixed
stage: -> committed/rejected
status: open -> closed
___
Python tracker
<http://bugs.python.or
Changes by R. David Murray :
--
type: -> enhancement
___
Python tracker
<http://bugs.python.org/issue14428>
___
___
Python-bugs-list mailing list
Unsubscri
Changes by R. David Murray :
--
nosy: +r.david.murray
type: -> enhancement
___
Python tracker
<http://bugs.python.org/issue13238>
___
___
Python-bugs-list mai
R. David Murray added the comment:
Thanks for the report.
I'm not familiar with multiprocessing, so I'll have to leave it to someone else
to judge the fix.
We use 'crash' to indicate a segfault in the Python interpreter, so I'm
changing the type to 'be
R. David Murray added the comment:
I'm not seeing any unhighlighted examples in that section.
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/is
Changes by R. David Murray :
--
nosy: +bethard
versions: +Python 3.3 -Python 2.7
___
Python tracker
<http://bugs.python.org/issue14504>
___
___
Python-bugs-list m
R. David Murray added the comment:
Which version of python did you test with? There have been several
improvements html parsing recently.
--
nosy: +ezio.melotti, r.david.murray
___
Python tracker
<http://bugs.python.org/issue14
R. David Murray added the comment:
I just tested your script on 3.2.3a2+, and it raises an error. Ezio made the
other parsing changes, I'll leave it to him to evaluate what if anything should
be done here.
--
versions: +Python 3.3
___
P
R. David Murray added the comment:
Berker: you can reproduce the bug, or the fact that they are highlighted? The
png looks like they are highlighted, so I assume the latter.
--
___
Python tracker
<http://bugs.python.org/issue14
R. David Murray added the comment:
Ah, you mean they are not *syntax* highlighted. Now I understand. Sorry for
missing that.
My understanding is that Sphinx does not use Python directly to parse the code
and highlight it, it uses pygments, which uses regexes. So this basically
amounts to
R. David Murray added the comment:
Huh. Well, in another issue Georg said it was now possible to upgrade the doc
build toolchain to Python3.
--
___
Python tracker
<http://bugs.python.org/issue14
R. David Murray added the comment:
No, you need to be able to pass bytes to Popen, just like you do to the
os.exec[xx] functions. When the OS doesn't fully support unicode, that is
sometimes the only option. As for filenames; again, as long as the underlying
systems use bytes filenam
R. David Murray added the comment:
I'm getting 'malformed patch at line 30' when I try to apply your patch.
Also, while it's not wrong, I don't think there's much point in catching the
NameError and doing a fail. The second Exception clause is definitely wrong
New submission from R. David Murray :
A common pattern (especially in writing tests) is to create a named temporary
file, operate on it with tools that take the filename, and then delete the
file. This pattern would be facilitated by a version of NamedTemporaryFile
that deleted the named
New submission from R. David Murray :
The title pretty much says it all. I believe the behavior is correct (more
useful than returning an object that is only useful for obtaining the name)
even though it is unusual for context managers. In any case there is plenty of
code using the existing
R. David Murray added the comment:
Grr. I did a search first, and even used google because I know search is
currently broken, and I did not find that issue.
--
___
Python tracker
<http://bugs.python.org/issue14
R. David Murray added the comment:
See issue 14514 for an alternate proposal to solve this. I did search before I
opened that issue, but search is currently somewhat broken and I did not find
this issue. I'm not marking it as a dup because my proposal is really a new
fe
R. David Murray added the comment:
Thanks, Popa. I made some style changes to the tests, but otherwise used your
patch. One small note: your might want to see about setting your editor to
show whitespace at the ends of lines, or use the 'make patchcheck' command to
check for
R. David Murray added the comment:
If one changes the stacklevel in the DeprecationWarnings in the library to '2'
instead of '1' (I believe it should be '2'), then an interesting array of
deprecation warnings are issued...including from cookiejar code.
Most of
R. David Murray added the comment:
It doesn't matter *how* you get to the situation where you are releasing a lock
that hasn't been acquired, the point is to document what actually happens when
you do the release. And just yesterday I needed to know this, since I have a
lock that
R. David Murray added the comment:
I, on the other hand, would prefer if it were made part of the API contract
that an error is raised, and to fix any stdlib implementations *of that API*
that don't conform to that. (That is, locks from other modules may well not
follow that API, and
Changes by R. David Murray :
--
type: -> enhancement
___
Python tracker
<http://bugs.python.org/issue14518>
___
___
Python-bugs-list mailing list
Unsubscri
R. David Murray added the comment:
The documentation appears to be correct to me. Can you demonstrate your
suggestion with some examples?
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/issue14
R. David Murray added the comment:
Is this a bug report about configure, or a bug report about a crash during
compilation after you've adjusted the configure parameters? It seems like you
are reporting two different things here.
For the configure issue, would you care to suggest a patc
R. David Murray added the comment:
Can you suggest a patch? As I said on the other issue I don't believe any core
developers have access to hpux.
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/is
R. David Murray added the comment:
To quote Martin from an older issue: "Python on HP-UX has never really worked
well, but it has worked in some fashion for a long time". IA64 probably
introduces a whole slew of new issues. If you can work through them and
suggest patches tha
R. David Murray added the comment:
Oh, and python2.6 is in security-fix only mode, so any fixes would only go into
go into 2.7 and later. Have you gotten as far as trying to reproduce this on
2.7?
--
___
Python tracker
<http://bugs.python.
R. David Murray added the comment:
Oh, wait, I see you are testing the security RC. Is this a new problem, or
does it also occur with the previous released version of 2.6?
--
___
Python tracker
<http://bugs.python.org/issue14
R. David Murray added the comment:
To clarify what Serhiy said about the patches, the link to the patch works, but
the Reitveld review button isn't working. I get 'No issue exists with that id
(6972)'.
--
nosy: +loewis
___
Python
R. David Murray added the comment:
Can you clarify? In what sense has the 2.7.3 rc regressed?
--
___
Python tracker
<http://bugs.python.org/issue14526>
___
___
New submission from R. David Murray :
The attached patch makes 'test_main' optional for stdlib tests. If a test
module does not have a 'test_main', regrtest will use the unittest
loadTestsFromModule loader to load the tests.
This moves us further in the direction of u
R. David Murray added the comment:
I can't imagine when you'd *not* want setUpModule/tearDownModule to run, so
that's a reasonable conversion path. The other path for reap_children and
reap_threads would be to apply them to the individual classes that require them
within
R. David Murray added the comment:
I think dummy_threading should be fixed (but only in 3.3, just in case it
causes any backward compatibility issues with someone's code).
Logging I'd leave to Vinay to decide about.
I'm assuming that if any of the others devs nosy on this issu
R. David Murray added the comment:
David, thanks for your assistance. I didn't wind up using your patch, but the
work you did was valuable in preparing the patch I committed.
What I did was turn your 'detect the attributes' recipe into a unit test. I
then applied your patch
R. David Murray added the comment:
I'm sorry, but the bug tracker isn't a good place to get help. You'll have
better luck getting assistance for this on the python-list mailing list (see
mail.python.org).
--
nosy: +r.david.murray
resolution: -> invalid
stage: -&g
New submission from R. David Murray :
A common pattern in testing is to have a base test class that implements test
methods, and subclasses that provide various data that drives the tests to be
run in different ways. It is convenient for the base class to inherit from
TestCase, but this
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:
Antoine: I don't have any problem with that personally, but Michael did, and
he's the maintainer :)
But there is a small advantage: it means you don't have to keep repeating the
'unittest.TestCase' boilerplate in each subclass decl
Changes by R. David Murray :
--
nosy: +vinay.sajip
___
Python tracker
<http://bugs.python.org/issue14539>
___
___
Python-bugs-list mailing list
Unsubscribe:
R. David Murray added the comment:
Note that I did just document the mixin idiom in the Lib/test docs. Which core
developers probably don't read :)
--
___
Python tracker
<http://bugs.python.org/is
R. David Murray added the comment:
"delete_after" what? I know it is somewhat implicit in the fact that it is a
context manager call, but that is not the only context the method name will be
seen in. (eg: 'dir' list of methods, doc index, etc). Even as a context
manager
R. David Murray added the comment:
By the way, I still think it would be nicer just to have the context manager
work as expected with delete=True (ie: doesn't delete until the end of the
context manager, whether the file is closed or not). I'm OK with being voted
down on th
R. David Murray added the comment:
Well, fixing NamedTemporaryFile in either of the ways we've discussed isn't
going to fix people writing non-portable code. A unix coder isn't necessarily
going to close the file before reading it. However, it would at least
significantly in
R. David Murray added the comment:
Thanks for the patch.
Do you have any interest in writing a test for this? Tests for tools go in
Lib/test/test_tools.py.
--
nosy: +r.david.murray
stage: -> test needed
type: -> behavior
versions: +Python 3.2, Python 3.3 -Pyth
R. David Murray added the comment:
It would also be reasonable to add a comment to the code mentioning why this
particular (security) comparison is *not* vulnerable to a timing attack, which
would serve the education purpose if someone does look at the code.
--
nosy: +r.david.murray
R. David Murray added the comment:
The content of a symbolic symlink is a symbolic reference to another location
in the file system. If you had used a hard link it would certainly work as you
expected.
The behavior with respect to symbolic links ought to be documented here:
http
R. David Murray added the comment:
I misread the docs. They aren't wrong, but it is still the case that they
don't mention that the directory name is what you get on entry to the context,
which is what led to my confusion.
Here's a patch.
--
keywords: +patch
nosy:
New submission from R. David Murray :
This was removed in 2cf7bb2bbfb8 along with a bunch of other functions. Yet in
issue 13959 Brett mentions needing to implement it. I don't see any
replacement for its functionality in importlib, so I would think it would be a
function we would wa
R. David Murray added the comment:
Thanks for the patch. I don't think you ran the test though, since it didn't
pass, and there was a mistake in your patch :)
I had to change the test considerably, and only applied the test part on 3.3
since I used mock.
--
resolution:
R. David Murray added the comment:
OK, the text at the start of the section, that I didn't notice in the 2.7 docs,
says they are obsolete and replaced by find_module and import_module. But
load_source is much more convenient, so I for one am not going to remove my use
of it in the te
Changes by R. David Murray :
--
type: -> enhancement
___
Python tracker
<http://bugs.python.org/issue14555>
___
___
Python-bugs-list mailing list
Unsubscri
R. David Murray added the comment:
Thanks.
--
nosy: +r.david.murray
resolution: -> fixed
status: open -> closed
type: -> behavior
___
Python tracker
<http://bugs.python.or
New submission from R. David Murray :
2.7 d60ef141e090
3.2 f25fb7e1d076
3.3 bd353f12c007
Thanks.
--
nosy: +r.david.murray
resolution: -> fixed
stage: -> committed/rejected
status: open -> closed
type: -> behavior
___
Python tr
R. David Murray added the comment:
Serhiy: this looks good. I get some test errors when I apply it on 2.7 though.
Would you be interested in doing a 2.7 version as well?
(Minor comment: the test method would be better as two test methods, and it
would be nice to have a third test method
R. David Murray added the comment:
Serhiy: this looks good. I get some test errors when I apply it on 2.7 though.
Would you be interested in doing a 2.7 version as well?
(Minor comment: the test method would be better as two test methods, and it
would be nice to have a third test method
Changes by R. David Murray :
--
Removed message: http://bugs.python.org/msg158095
___
Python tracker
<http://bugs.python.org/issue14399>
___
___
Python-bugs-list m
R. David Murray added the comment:
Can you point to the changes you think are at issue? That might help us track
down why the change was made. This isn't necessarily a bug, but even if it
isn't, the behavior should probably be explicitly documented.
--
nosy:
R. David Murray added the comment:
Ah, so there are actually two timeouts of interest. One is "time out if there
is no more data for X seconds", and the other is "time out if there is no match
for X seconds". It used to do the former, now it does the latter.
I think y
R. David Murray added the comment:
Thanks.
We've had trouble in the past with a conversion to new style class breaking
people's code. People are less likely to be subclassing ZipFile, though, so it
is probably OK.
--
___
Python trac
R. David Murray added the comment:
It is fixed in Python3. Apparently Raymond was wrong about it having been
fixed earlier (or perhaps he was referring to the unicode being removed from
the pydoc __credits__ string).
--
nosy: +r.david.murray
R. David Murray added the comment:
Yes, after considerable discussion those of working on this stuff decided that
the goal should be that the parser be able to complete parsing, without error,
anything the typical browsers can parse (which means, pretty much anything,
though that says
R. David Murray added the comment:
Search is currently not returning all matching issues, unfortunately. You
might get a few more hits by searching for hpux in the title field via advanced
search.
--
nosy: +r.david.murray
___
Python tracker
R. David Murray added the comment:
Thanks, Serhiy.
I made one small change, using 'with self.assertEqual' in the TypeError test.
You might want to check that out, it is a useful technique.
Oh, and I removed the type check from the 2.7 patch. You can use a unicode
string as
R. David Murray added the comment:
I mean "with self.assertRaises(TypeError):".
--
___
Python tracker
<http://bugs.python.org/issue14399>
___
___
R. David Murray added the comment:
Ah. I based that on the fact that the third test passed without the change. I
thought you were adding that test of changing the comment just as a double
check. I should have asked instead of assuming
R. David Murray added the comment:
I must have been seeing what I expected to see. The test that failed was the
non-empty test.
News item fixed, thanks for the correction.
--
___
Python tracker
<http://bugs.python.org/issue14
Changes by R. David Murray :
--
title: imaplib.IMAP4.authenticate authobject fails with PLAIN mechanism ->
imaplib.IMAP4.authenticate authobject does not work correctly in python3
___
Python tracker
<http://bugs.python.org/issu
R. David Murray added the comment:
It works fine if you use unicode.
--
nosy: +r.david.murray
resolution: -> invalid
stage: -> committed/rejected
status: open -> closed
___
Python tracker
<http://bugs.python.or
R. David Murray added the comment:
Indeed, this type of confusion is a large part of the motivation behind Python3.
You might try posting to the python-list mailing list asking for help if for
some reason you are required to use python2 for your program
R. David Murray added the comment:
It certainly is worthwhile pursing this in some fashion, since at the very
least the existing error message needs to be improved. But perhaps there is
something more that can be done to gracefully handle this case, instead. I
think the next interesting
R. David Murray added the comment:
The suggested doc change won't work, since that would imply that the size
argument was required. We'd have to use the old truncate([size]) notation.
Supporting it as a keyword argument is probably to be preferred, but someone
will have to write
R. David Murray added the comment:
Hmm. 2.5 years later it isn't looking like we are going to get a response.
Closing.
--
nosy: +r.david.murray
resolution: -> works for me
stage: -> committed/rejected
status: open -> closed
___
Changes by R. David Murray :
--
assignee: -> lukasz.langa
nosy: +lukasz.langa
___
Python tracker
<http://bugs.python.org/issue14590>
___
___
Python-bugs-lis
2601 - 2700 of 10554 matches
Mail list logo
