R. David Murray added the comment:
That said, the fact that windows is just *wrong* about some mimetypes is
definitely an issue. We could call it a platform bug, but that would be a
disservice to the user community.
--
___
Python tracker
<h
R. David Murray added the comment:
To be consistent with the overall philosophy of the mimetypes module, it should
be instead a list of "windows fixes" which are applied if the broken mimetype
is found in the windows registry.
If you want to avoid the overhead, pass an empty list t
Changes by R. David Murray :
--
nosy: +dmalcolm
___
Python tracker
<http://bugs.python.org/issue16637>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from R. David Murray:
>From the docs it isn't quite clear if getfqnd() does the equivalent of:
gethostbyaddr('127.0.0.1')
or
gethostbyaddr(gethostbyname(gethostname()))
It matters which it is, when debugging a host's name configuration a
R. David Murray added the comment:
The statement
print "hello world"
is indeed invalid syntax in Python3.
--
nosy: +r.david.murray
resolution: -> invalid
stage: -> committed/rejected
status: open -> closed
___
Py
R. David Murray added the comment:
I'm personally OK with the option of removing the registry support (or making
it optional-by-default), but I'm not going to make that call, we need a windows
dev opinion.
Maintaining the list of windows exceptions shouldn't be much worse th
R. David Murray added the comment:
No.
--
nosy: +r.david.murray
resolution: -> out of date
status: open -> closed
___
Python tracker
<http://bugs.python.org/i
R. David Murray added the comment:
Oops, clicked submit too soon.
It isn't likely to get fixed in 2.7, because 2.7's unicode support problems is
the major reason python3 was developed.
--
stage: -> committed/rejected
___
Python t
R. David Murray added the comment:
For that matter, it isn't reproduced in python2.7, either:
>>> for r, dirs, files in os.walk(u'.'):
... print dirs
...
[u'\u0420\u0443\u0441\u0441\u043a\u043e\u0435 \u0438\u043c\u044f']
[]
--
R. David Murray added the comment:
Works for me without the u'.', too, though less usefully:
>>> for r, dirs, files in os.walk('.'):
... print dirs
...
['\xd0\xa0\xd1\x83\xd1\x81\xd1\x81\xd0\xba\xd0\xbe\xd0\xb5
\xd0\xb8\xd0\xbc\xd1\x8f']
Maybe that
R. David Murray added the comment:
I would say Brian Curtin, Tim Golden, and/or Martin von Löwis, as
they are the currently active committers with significant Windows expertise.
Other committers may have opinions as well. If you don't get an answer here in
a reasonable amount of time, p
R. David Murray added the comment:
My guess is that your unicode issue is issue 1602, which is non-trivial to
solve.
--
___
Python tracker
<http://bugs.python.org/issue16
R. David Murray added the comment:
test_email is a package, and has a load_tests in its __init__.py that I had to
add in order to make "python -m unittest test.test_email" work. So I'm not
sure what bug you are reporting here.
--
nosy:
R. David Murray added the comment:
Based on the pasted results I'm pretty sure there's nothing wrong with walk and
listdir. But it sounds like Serhiy will check to make sure, so we'll wait for
his report.
The byte string vs the coding cookie is an interesting observation, but
R. David Murray added the comment:
That is indeed our standard policy. And yes, thank you for trying, Raninho. A
good way to make an initial contribution is to look for modules that don't yet
have full test coverage (there are a lot) and add tests. The devguide
(http://docs.pytho
R. David Murray added the comment:
Matt, thanks for your interest. This possibility has been discussed, so you
aren't the only one who thinks it should happen.
However, I don't think this is an appropriate issue for the tracker. This is
part of an ongoing discussion and process on
R. David Murray added the comment:
We aren't encouraging people to use optparse any more. The recipe isn't needed
in argparse, as that has a "parse_known_args" method that achieves the same end.
--
nosy: +r.david.murray
___
P
R. David Murray added the comment:
That's what surrogateescape is for, on linux. I thought Victor dealt with this
a different way in Windows. Maybe by deprecating the bytes interface :)
--
nosy: +haypo
___
Python tracker
<http://bugs.py
R. David Murray added the comment:
Ah, I misunderstood your comment.
So, listdir is returning the "correct" the filename, it's just that we can't
encode it to the console encoding. So, it is working as expected within the
current windows console limitations, if not in a
R. David Murray added the comment:
Oh, I remember Victor complaining about that behavior of Windows. I'm pretty
sure it is the windows API and not python that is doing that mangling. But
Victor would know for sure.
--
___
Python tracker
Changes by R. David Murray :
--
resolution: -> out of date
stage: -> committed/rejected
status: open -> closed
___
Python tracker
<http://bugs.python.or
New submission from R. David Murray:
>>> import collections
[61531 refs, 20955 blocks]
>>> eval('foo', {}, collections.ChainMap(object()))
python: Python/ceval.c:2996: PyEval_EvalFrameEx: Assertion `0' failed.
zsh: abort ./python
--
messages: 177542
R. David Murray added the comment:
This is a duplicate of issue issue 16468, which may get closed with either a
bug fix or a doc fix, depending on the outcome of the overall discussion.
--
nosy: +r.david.murray
resolution: -> duplicate
stage: -> committed/rejected
status
Changes by R. David Murray :
--
nosy: +wim.glenn
___
Python tracker
<http://bugs.python.org/issue16468>
___
___
Python-bugs-list mailing list
Unsubscribe:
R. David Murray added the comment:
Well, it is effectively documented by the text here:
http://docs.python.org/3/reference/simple_stmts.html#augmented-assignment-statements
since "a + b" is logically equivalent to a.extend(b) when a is being updated
"in-place". Th
New submission from R. David Murray:
It works fine for me. Are you on windows by any chance? I suspect you should
take this to python-list for help, but you could paste the traceback you are
getting if you still think it is a bug in Python.
--
nosy: +r.david.murray
resolution
R. David Murray added the comment:
You have a 'copy.py' module in your python path, as is evidenced by the
filename in your traceback, which tarfile is importing instead of the real copy
module, and your copy.py is therefore trying to use shutil before it is
completely imported
R. David Murray added the comment:
It seems sensible to me.
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/issue16716>
___
___
Python-bug
R. David Murray added the comment:
No, that would be a feature addition, and we don't do those in bug fix releases.
--
nosy: +r.david.murray
resolution: -> rejected
stage: -> committed/rejected
status: open -> closed
___
Python
R. David Murray added the comment:
We do not use data type names as formal parameter names. You will realize this
is sensible if you consider that in most cases in Python the formal parameter
name is something gets used in more than just the documentation, and that using
a type name would
R. David Murray added the comment:
I'm imagining that it creates jar files, and thus has the signature as a
constant. The is_zipfile check is much more complicated than just looking for
that string, though, so what is going on must be even more perverse than that.
It would be interesti
R. David Murray added the comment:
So, it looks like this is not a bug in Python, just a weirdness of fastjar.
Or, if you prefer, a bug in fastjar (they could assemble the signature instead
of coding it as a single constant).
--
resolution: -> invalid
stage: -> committed/re
R. David Murray added the comment:
Well, yes, but that ship has already sunk :)
--
___
Python tracker
<http://bugs.python.org/issue16735>
___
___
Python-bug
R. David Murray added the comment:
The editors do more than your sentence suggests. They also (sometimes) edit
peps, (sometimes) provide advice about preparing one, and commit and update
peps when the author(s) do not have commit access.
The distinction in the types of email that PEP 1 is
R. David Murray added the comment:
Given the error message, my guess would be that there is a bug in the
Solidoodle Python extension module. That is, it is unlikely to be a bug in
Python.
--
nosy: +r.david.murray
___
Python tracker
<h
R. David Murray added the comment:
Not really, I'm afraid. You'd have to look at the crash dump in a debugger to
get more useful information. Perhaps one of the windows devs will have more
concrete advice, I don't use
Changes by R. David Murray :
--
nosy: +michael.foord
___
Python tracker
<http://bugs.python.org/issue16751>
___
___
Python-bugs-list mailing list
Unsubscribe:
R. David Murray added the comment:
I am -1 on doing this as one big refactoring, unless tests are written for
regrtest first. Incremental (over a period of weeks or months, so that the
changes get some soak time each time) is I think acceptable even without tests,
given that this is a test
R. David Murray added the comment:
Yes, I apologize for not getting around to a review previously.
Chris: why regrlib.py at all? Why isn't the code in regrtest.py? And I'm not
clear on why there is a desire to have regrtest be a package. Did I miss that
R. David Murray added the comment:
Thanks for the report, however WINE is not an environment we support. A quick
google indicates people have occasionally succeeded in getting it to install
and run (for some definition of run), but it sounds like you've read about
those.
If you want to
Changes by R. David Murray :
--
nosy: +vinay.sajip
___
Python tracker
<http://bugs.python.org/issue16778>
___
___
Python-bugs-list mailing list
Unsubscribe:
R. David Murray added the comment:
The bug tracker is not a place to get help, but is rather for reporting bugs
and proposing patches.
We do not currently support msys/mingw. As you have observed, various patches
have been proposed; however, in order for any of them to get committed, we need
R. David Murray added the comment:
The fact that the print works should be a clue that Python is in fact finding
the module and importing it. So your problem actually has to do with
namespaces, which is something you have to think about when using exec or
execfile. You can see this by
Changes by R. David Murray :
--
nosy: +bethard
___
Python tracker
<http://bugs.python.org/issue16786>
___
___
Python-bugs-list mailing list
Unsubscribe:
R. David Murray added the comment:
I'm still -0 on making a new file. regrtest will be running as __main__, so I
don't see any reason the test file can't import it to test functions within it.
--
___
Python tracker
<http
R. David Murray added the comment:
(I could, of course, be wrong :)
--
___
Python tracker
<http://bugs.python.org/issue15302>
___
___
Python-bugs-list mailin
R. David Murray added the comment:
Do you mean that *modifying* locals() in the function scope is undefined
behavior? That makes sense, and is a documented limitation.
So we need to clarify the execfile/exec documentation to note that if called in
anything other than the global scope, locals
R. David Murray added the comment:
Yes, the behavior here is "undefined" at the language level. And as pyos says,
technically it is documented: if you mutate the object over which you are
iterating inside the iteration context (a for loop is just one example of
same), the b
R. David Murray added the comment:
This is a duplicate of issue 10060, and as indicated there there really isn't
much Python can do about this. You should report the bug to Ubuntu, but I'm
pretty sure there is already a bug in their system for it (which I believe has
R. David Murray added the comment:
If it is a feature, then is it documented in the language reference and is this
actually a bug in PyPy (it sounds like it is)?
--
___
Python tracker
<http://bugs.python.org/issue16
R. David Murray added the comment:
I don't think you mean 'docstring'. A docstring is something a human writes in
the source code. I presume you are actually talking about introspection of the
signature here. Beyond that, I agree with Mark's comments.
--
n
R. David Murray added the comment:
That sounds right to me.
Note that PEP 399 is following older conventions that were laid down in a time
when unittest did not *have* test discovery, so this is a new paradigm we'd
like to move to (for the reasons Brett mentioned), and it may take a whi
R. David Murray added the comment:
It looks like you are correct Terry. The problem, I think, is that the
behavior of name spaces inside a class definition is probably the least
intuitive aspect of python scoping, so that sentence, while technically
complete, doesn't provide enough gui
Changes by R. David Murray :
--
components: +email
nosy: +barry, r.david.murray
stage: -> needs patch
type: crash -> behavior
versions: +Python 3.4
___
Python tracker
<http://bugs.python.org/i
R. David Murray added the comment:
Thanks for the report.
We thought we fixed this once already (in issue 11401). It looks like that
only fixed the "old" folding algorithm, and that the new one has the same bug.
I thought the test ran against both algorithms, but I must have made
R. David Murray added the comment:
Thanks for the suggestion, but the context is that you are in the Doc directory
in order to run make, so I think the existing documentation is preferable. I'd
let George decide, though.
--
nosy: +georg.brandl, r.david.murray
title: use
R. David Murray added the comment:
I think the fact that the cd paradigm is more commonly encountered is a fairly
strong argument in favor of keeping it, but I'm only -0 on this change.
--
nosy: +r.david.murray
___
Python tracker
Changes by R. David Murray :
--
title: use --directory option of make -> use --directory option of make in
describing how to build the docs
___
Python tracker
<http://bugs.python.org/issu
R. David Murray added the comment:
As Nick pointed out in the thread, getting the correct module imports for C and
python versions is what import_fresh_module in test.support is for.
--
nosy: +r.david.murray
___
Python tracker
<h
R. David Murray added the comment:
Hmm. What if we made import_fresh_module a context manager, so that the
restore of the original module in sys.modules only happened at the end of the
context?
--
___
Python tracker
<http://bugs.python.
R. David Murray added the comment:
It would help because import_fresh_module would have updated sys.modules to be
the module under test, and would not restore the previously existing entry in
sys.modules until after your test had completed
Changes by R. David Murray :
--
nosy: +lukasz.langa
___
Python tracker
<http://bugs.python.org/issue16820>
___
___
Python-bugs-list mailing list
Unsubscribe:
R. David Murray added the comment:
senthil: the file type doesn't exist any more in python3.
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/is
R. David Murray added the comment:
I wonder if this is related to issue 16778.
--
nosy: +r.david.murray, vinay.sajip
___
Python tracker
<http://bugs.python.org/issue16
R. David Murray added the comment:
The FAQ (as in, this question gets asked again and again) is something like
"why do the lambdas I define in a loop all return the same result when the
input value was different when each one was defined?"
The same applies to regular functions,
R. David Murray added the comment:
Could you give more information about what you see as the bug, here? I'm not
understanding the problem because there doesn't appear to be enough context.
What is your directory structure? Where is the import happening?
--
components: +I
R. David Murray added the comment:
I would suggest one patch and issue per test module. If multiple test modules
are related enough, they could go in one patch/issue; that's a judgement call.
We can make this issue dependent on those individual i
R. David Murray added the comment:
The point is, it is a FAQ. We are talking about updating the FAQ document. It
doesn't matter if the text is "too specific", if it is in fact a FAQ. And it
is.
--
___
Python tracker
<http
R. David Murray added the comment:
But that's about numpy, which is not part of core Python, and so doesn't belong
in a Python FAQ. But perhaps your posting it here will help someone doing an
internet search...
--
nosy: +r.david.murray
R. David Murray added the comment:
Confirmed on Gentoo linux. On default, too. This is a regression from 3.2.
--
nosy: +r.david.murray
versions: +Python 3.4
___
Python tracker
<http://bugs.python.org/issue16
R. David Murray added the comment:
Ah, the whole tutorial is newish. So this is a bug just in the 2.7 version of
the tutorial (it doesn't match the 2.7 code), and yes, there may be other
issues as well.
--
___
Python tracker
R. David Murray added the comment:
Actually it looks like it is future-dated. The documented error message is the
one you get from 3.3. I guess someone backported a doc change for a feature
change.
--
nosy: +r.david.murray
___
Python tracker
R. David Murray added the comment:
See issue 14034. Ezio apparently left the error messages unchanged on
purpose...I'm not sure why.
--
assignee: docs@python ->
nosy: +ezio.melotti, tshepang
___
Python tracker
<http://bugs.python.org
R. David Murray added the comment:
Considering that sqlite's 'replace' is a synonym for 'insert or replace', I
think the logic error is actually in the detect_statement_type function. Since
actions are conditionally taken on the REPLACE statement type in the code,
in
R. David Murray added the comment:
Looks good to me.
--
___
Python tracker
<http://bugs.python.org/issue13094>
___
___
Python-bugs-list mailing list
Unsubscribe:
R. David Murray added the comment:
This is intentional. You have to call expanduser yourself if you want ~ to be
expanded. Otherwise it is treated as any other path component would be.
I don't understand your final comment, can you clarify?
--
nosy: +r.david.murray
resol
R. David Murray added the comment:
I'd prefer to fix it, since having the action='append' and nargs='*' behaviors
be different looks like a bug. However, fixing it to match 'append' (default
really is None) would be likely to break working code, so we cer
R. David Murray added the comment:
In addition, as far as I know, ba/sh has no equivalent to os.path.join (see,
eg: http://unix.stackexchange.com/questions/23208/building-paths-robustly). So
even if we *did* want to "act like the shell" there's no analog to point to.
The she
R. David Murray added the comment:
Here is a proposed doc patch. While not a necessary doc addition, I do think
it provides some useful guidance, and is short enough that it doesn't weigh
down the docs.
--
keywords: +patch
Added file: http://bugs.python.org/file
R. David Murray added the comment:
>>> p.add_argument('-a', action="append", default=None)
>>> p.parse_args([])
Namespace(a=None)
>>> p.parse_args(['-a', '1', '-a', '2'])
Namespace(a=['1', '
R. David Murray added the comment:
I'm afraid the discussions are many and lengthly and on several lists
(python-dev, distutils-sig, probably also python-list and python-ideas), and
that you will rarely find a discussion of "whether" without an accompanying
discussion of "
R. David Murray added the comment:
Great list, thanks.
The ones that fail to be run/skipped when run under discovery can probably be
fixed by moving them to the more modern unittest 'skip' functions instead of
depending on being run under regrtest and using the test.suppor
R. David Murray added the comment:
As we discussed in another issue, you just need to change your pattern to:
>>> import unittest.main as runtest
>>> import test.test_xxx as t
>>> runtest(t)
Which granted is more typing if you are running just one test, but not mu
R. David Murray added the comment:
I agree that this would be useful.
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/issue16613>
___
___
Pytho
R. David Murray added the comment:
Yes, but not many, and not as many as there used to be. I'd like to see them
all moved, but met resistance on that front. It may be that those just can't
be run using unittest discovery, and perhaps that will eventually convince the
maintaine
R. David Murray added the comment:
Also, it may be possible to add unittest discovery hooks to the stubs that
*are* in Lib/test.
--
___
Python tracker
<http://bugs.python.org/issue16
R. David Murray added the comment:
> So it looks like if "import xyz.b" bahaves different depending on how
> a.py was initially loaded as a script or imported from another module.
There are several differences between importing a module and running a script,
one of whi
Changes by R. David Murray :
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/issue16509>
___
___
Python-bugs-list mailing list
Unsubscribe:
R. David Murray added the comment:
For the record, this is a regression introduced by the fix for issue 9750. I
plan to commit the fix shortly, thanks for the report and patch.
--
nosy: +r.david.murray
stage: -> commit review
type: crash -> behavior
versions: +Python 2.7, Pyth
R. David Murray added the comment:
For the record, this patch also introduced another regression (issue 15545).
--
___
Python tracker
<http://bugs.python.org/issue9
R. David Murray added the comment:
Peter, I see you've made contributions before, but you don't show as having a
contributor agreement on file according to the tracker. Have you sent one in?
If not, would you, please?
Thanks again for the fix.
--
components: +Library (
Changes by R. David Murray :
--
components: +email
nosy: +barry, r.david.murray
stage: -> patch review
___
Python tracker
<http://bugs.python.org/issu
Changes by R. David Murray :
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/issue8145>
___
___
Python-bugs-list mailing list
Unsubscribe:
R. David Murray added the comment:
I believe that the complete list of test files still located outside of
Lib/test are:
tkinter/test
distutils/tests
ctypes/tests
lib2to3/tests
sqlite3/test
unittest/test
That last is somewhat ironic since Michael opened the issue :).
I&#
R. David Murray added the comment:
Talked to Michael in IRC. He isn't particularly in favor of the move of the
unittest tests, but doesn't object if someone else wants to do it. So,
unassigning the issue from him.
--
assignee: mic
R. David Murray added the comment:
These patches are small enough a contributor agreement is not required, but it
would still be great if you would submit one, poq.
--
nosy: +r.david.murray
stage: patch review -> committed/rejected
status: open ->
Changes by R. David Murray :
--
resolution: -> fixed
stage: needs patch -> committed/rejected
status: open -> closed
___
Python tracker
<http://bugs.python.or
R. David Murray added the comment:
Print b happens when the interpreter is processing the loop condition for loop
c. print c happens when it is processing the body of the loop (ie: is inside
the try/except in the body of the loop). Presumably if you set your keyboard
autorepeat interval
R. David Murray added the comment:
I believe this patch is correct in essence, but I think it would be helpful to
clarify the explanation of what autocommit mode is. I'll work on an updated
patch.
It could also be considered a bug that the standard context manager does not
su
R. David Murray added the comment:
I'm not positive what Terry means by export patch and import patch...I think hg
actually has commands like that, but I don't use them myself. I just use hg
diff to generate the diff/patch file, and then use the regular patch command to
apply
5301 - 5400 of 10554 matches
Mail list logo
