New submission from Chris Rebert :
http://docs.python.org/py3k/library/os.html currently mentions os.popen() in
several places. The docs for os.popen() itself say:
'These functions are described in section "File Object Creation"'
However, unlike the 2.x version of
Changes by Chris Rebert :
Added file: http://bugs.python.org/file18209/subprocess.rst.diff
___
Python tracker
<http://bugs.python.org/issue7950>
___
___
Python-bugs-list m
Chris Rebert added the comment:
My apologies for the extra email...
--
Added file: http://bugs.python.org/file18210/subprocess.rst.diff
___
Python tracker
<http://bugs.python.org/issue7
Changes by Chris Rebert :
Removed file: http://bugs.python.org/file18209/subprocess.rst.diff
___
Python tracker
<http://bugs.python.org/issue7950>
___
___
Python-bug
New submission from Chris Leaf :
I have been using IDLE on my previous laptop and it was working well although I
have to say I'm still very new to python. I've read around about the issue and
can't find any solution I can use. I can run the IDLE GUI through the python
command
Chris Leaf added the comment:
Also the IDLE that I do manage to get open really doesn't work correctly, more
errors appear on the command line console as I try to do things like close the
IDLE window. So that doesn't serve as a useful t
Chris Leaf added the comment:
I can clear the attributes from the properties window of the folder but if I
remove them both it will automatically reset it back to Read Only every time i
close the properties window. I can get it to be hidden but I can't make it
permanently avai
Chris Leaf added the comment:
The hidden field is not filled in, here's a screenshot of the attributes options
--
Added file: http://bugs.python.org/file18240/Attributes.JPG
___
Python tracker
<http://bugs.python.org/i
Chris Leaf added the comment:
Upon trying to delete I'm prompted with an error:
Access is denied.
Make sure the disc is not full or write-protected and that the file is
currently not in use.
My disc isn't full and I cannot find anything accessing it (and the folder is
empty
Chris Leaf added the comment:
I also cannot get into the folder itself.
"Access Denied"
--
___
Python tracker
<http://bugs.python.org/issue9404>
___
___
Chris Leaf added the comment:
The problem is that I can do nothing to the folder at all
--
___
Python tracker
<http://bugs.python.org/issue9404>
___
___
Pytho
Chris Leaf added the comment:
Sorry but I still cannot get it to work because the folder remains inaccessible
to me and immutable. Is there any way around this problem?
--
___
Python tracker
<http://bugs.python.org/issue9
Chris Leaf added the comment:
I solved the problem myself by editing the EditorWindow.py file where it sets
self.recent_files_path by setting it to a different file location (I created a
file in my Python31 directory named recent-files.lst and then set the
recent_files_path to the absolute
Chris Withers added the comment:
What's email6 and where can I find out more about it?
Chris
--
___
Python tracker
<http://bugs.python.org/issue5612>
___
___
New submission from Chris Green :
When you call mailbox.mbox.add() the old mbox file is copied, the new file is
modified and then renamed to the name of the'old' mbox file.
This breaks the way that many MUAs detect and manage new mail in an mbox, in
particular I discovered this with
Changes by Chris Warrick :
--
nosy: +Kwpolska
___
Python tracker
<http://bugs.python.org/issue29134>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from Chris Barker:
In py3.5, the math.isclose() function was added to the standard library. It can
be used to compare floating point numbers to see if they are close to each
other, rather than exactly equal. It's not a lot of code, but there are nuances
that not every p
Chris Barker added the comment:
Thanks,
I'll add the equation to the docstring and docs.
As for adding a rel_tol to assertAlmostEqual -- I think that's a bad idea --
it's a pretty different concept -- overloading the same method would be more
confusing than anything el
Chris Barker added the comment:
updated patch with the equation in the docs.
--
Added file: http://bugs.python.org/file43165/assertClose.patch
___
Python tracker
<http://bugs.python.org/issue27
Chris Barker added the comment:
I'm not sure it's confusing --what would "close" mean for an assertion for a
file? "assertClosed" would be confusing -- and an even more trivial assert :-).
But we can bikeshed the name if we decide to put this in.
""&quo
Chris Barker added the comment:
thanks, that's Issue27152 if anyone's curious.
Though I have no idea why you'd want it in a mixin, rather than just there.
But sure, this could be "bundled" in with that.
Perhaps it's time for a broader discussion / consensus abo
Chris Barker added the comment:
Why a mixin rather than adding to TestCase? If they are useful they should be
easy to find.
Also, see Issue27198 for another possible new assert.
--
nosy: +ChrisBarker
___
Python tracker
<http://bugs.python.
Chris Barker added the comment:
Would that make folks more amenable to adding more "specialized" asserts? If
so, then sure.
I don't know that it takes a PEP (I hope not) but it would be good to have some
guidance as to the direction we want unittest to take written
Chris Barker added the comment:
"""w.r.t. error messages, a regular function that raises AssertionError with a
nice message will be precisely as usable."""
sure -- I totally agree -- but that's not the current unittest API :-( where
would you put it? How w
Chris Barker added the comment:
Thanks Raymond.
Damn! I wrote a nice comprehensive note, and my browser lost it somehow :-(.
Here's a shorter version:
"FWIW, I find assertClose easy to misinterpret. At first, it looks like an
assertion that a file is closed."
sure -- we can
New submission from Chris Withers:
This doesn't seem right:
(Pdb) ';;'
*** SyntaxError: EOL while scanning string literal
*** SyntaxError: EOL while scanning string literal
(Pdb) p ';;'
*** SyntaxError: EOL while scanning string literal
*** SyntaxError: EOL while sca
Changes by Chris Rebert :
--
nosy: +cvrebert
___
Python tracker
<http://bugs.python.org/issue23670>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Chris Rebert :
--
nosy: +cvrebert
___
Python tracker
<http://bugs.python.org/issue23496>
___
___
Python-bugs-list mailing list
Unsubscribe:
Chris Barker added the comment:
Did my comments not get posted, or are they not being read? Anyway:
Could we keep the issues separate here?
1) If you don't like the name, propose another name -- no none has defended
this name since an objection was first raised. I"m sure we can fin
Chris Barker added the comment:
Thanks Robert.
I'll try to find time to re-do the patch soon.
There was enough resistance to the whole idea that I wanted some confirmation
that is was worth my time to do that!
Stay tuned.
--
___
Python tr
Chris Jerdonek added the comment:
> Are there any issue *we* have with libffi which an update to 3.2.1 would
> solve ?
There are these Ubuntu-specific compiler warnings:
https://bugs.python.org/issue25077
which Berker says have been fixed in upstream libffi:
https://bugs.pyth
Changes by Chris Jerdonek :
--
nosy: +chris.jerdonek
___
Python tracker
<http://bugs.python.org/issue25077>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Chris Angelico :
--
nosy: +Rosuav
___
Python tracker
<http://bugs.python.org/issue27582>
___
___
Python-bugs-list mailing list
Unsubscribe:
Chris Angelico added the comment:
The question was raised that there might be a problem with (UTF-8) bytes vs
characters, but that's definitely not it - pythonrun.c:1362 UTF-8-decodes the
line of source and then gets its character length to use as the new offset. So
I don't think
Chris Angelico added the comment:
Actually pinpointing the invalid character may be impractical, as there are two
boolean situations: either a UnicodeDecodeError (because you had an invalid
UTF-8 stream), or PyUnicode_IsIdentifier returns false. Either way, it applies
to the whole identifier
Changes by Chris Angelico :
Added file: http://bugs.python.org/file43812/method2-change-cur-and-inp.patch
___
Python tracker
<http://bugs.python.org/issue27582>
___
___
Changes by Chris Angelico :
Added file:
http://bugs.python.org/file43814/method4-change-all-errors-if-possible.patch
___
Python tracker
<http://bugs.python.org/issue27
Changes by Chris Angelico :
Added file: http://bugs.python.org/file43813/method3-change-all-errors.patch
___
Python tracker
<http://bugs.python.org/issue27582>
___
___
Chris Angelico added the comment:
BTW, here's how a session looks using method 4's change:
>>> varname = asdf“d“a”t”apoint
File "", line 1
varname = asdf“d“a”t”apoint
^
SyntaxError: invalid character in identifier
>>> varname = asdf“d
Chris Angelico added the comment:
Hmm, that'd be curious. The code to do that is actually pretty simple - see
attached patch - but actually using that to affect error messages is a bit
harder. Is it safe to mess with tok->start?
--
Added file:
http://bugs.python.org/file438
Chris Angelico added the comment:
Attached is a combined patch that has the new private function for
IsIdentifier, method 4's error handling change, and a bit of glue in the middle
to make use of it. The result is a passing test suite (bar test_site which was
already failing on my system
New submission from Chris Angelico:
Originally reported (if you can call it "reported") here:
http://www.viva64.com/en/b/0414/
AFAICT, this is an easy and inconsequential fix.
--
files: uninitialized-pointer.patch
keywords: patch
messages: 270991
nosy: Rosuav
priority: norma
Chris Angelico added the comment:
Berker, I don't push code to CPython (I have the commitbit for PEP editing), so
do you want to push that?
--
___
Python tracker
<http://bugs.python.org/is
Chris Angelico added the comment:
Cool cool! Then someone will need to notify the PVS-Studio people that we've
fixed the two bugs that are actually our bugs :)
--
___
Python tracker
<http://bugs.python.org/is
Changes by Chris Rebert :
--
nosy: +cvrebert
___
Python tracker
<http://bugs.python.org/issue27561>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Chris Rebert :
--
nosy: +cvrebert
___
Python tracker
<http://bugs.python.org/issue27587>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Chris Angelico :
--
nosy: +Rosuav
___
Python tracker
<http://bugs.python.org/issue27587>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Chris Mayo :
--
nosy: +cjmayo
___
Python tracker
<http://bugs.python.org/issue25170>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Chris Mayo :
--
nosy: +cjmayo
___
Python tracker
<http://bugs.python.org/issue27226>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from Chris Jerdonek:
When installing Python 3.5.2 from source on Ubuntu 14.04 and running
make, I get the below "Could not find platform dependent libraries"
warnings (which I prefixed with "***" for better visibility).
>From this message which has more bac
Chris Angelico added the comment:
Here's a first-cut patch. No docs, no tests, and applies only to decimal
formatting. It involves redefining the thousands_separators flag from being a
boolean to being a three-state flag (none, comma, or underscore), and (ab)uses
LT_*_LOCALE to carry
Changes by Chris Angelico :
--
nosy: +Rosuav
___
Python tracker
<http://bugs.python.org/issue27080>
___
___
Python-bugs-list mailing list
Unsubscribe:
Chris Angelico added the comment:
Hmm, adding bin/oct/hex support didn't turn out that hard. Although it feels
like this code is getting hackish. Definitely needs code review!
--
Added file: http://bugs.python.org/file44153/underscores_all_bases.
Chris Angelico added the comment:
Hmm, strange. Comma formatting never seems to have had tests added. So I've
added a couple of simple tests of comma formatting at the same time as adding
underscore formatting tests. Also, test_long.py currently has a comment "#
octal" prece
Changes by Chris Jerdonek :
--
nosy: +chris.jerdonek
___
Python tracker
<http://bugs.python.org/issue27126>
___
___
Python-bugs-list mailing list
Unsubscribe:
Chris Jerdonek added the comment:
FWIW, I just came across an issue in Django's test suite that I believe is
caused by the issue reported here. Some of Django's unit tests were hanging for
me when run in "parallel" mode (which uses multiprocessing). Here is the ticket
Changes by Chris Angelico :
--
keywords: +patch
Added file: http://bugs.python.org/file44158/no-site-packages-in-test.patch
___
Python tracker
<http://bugs.python.org/issue27
New submission from Chris Angelico:
Having matplotlib installed globally causes test_site to fail, due to the .pth
file importing types. The point of the test is to monitor startup dependencies
(and thus time) for the core interpreter and standard library, not third-party
libraries, so having
Chris Jerdonek added the comment:
> We can't solve that problem; only Apple can;
> So, if we don't change _scproxy or urllib*'s use of it, only Apple can fix
> the problem.
In the Django ticket I mentioned in my comment above, one of the commenters
said, "Just r
New submission from Chris Wood:
Windows 7 / 64-bit / 4 Gb Ram / Intel i5 processor.
This seems to have been discussed intermittently in the past, but none of the
previous answers fixed my problem.
I installed 3.5, and when I tried running it (both from the Windows cmd line
and from the
Chris Wood added the comment:
https://www.python.org/downloads/
--
___
Python tracker
<http://bugs.python.org/issue27836>
___
___
Python-bugs-list mailin
Chris Wood added the comment:
Apologies, there are typos in my final paragraph - 3.5.11 should just be 3.5,
and 3.5.12 should be 3.5.2
--
___
Python tracker
<http://bugs.python.org/issue27
Chris Wood added the comment:
Ah, in that case:
- I guess the issue would have been that the python 3.5 installation I tried
(which was 3.5.0a1) had the vcruntime140.dll issue
- I've realised that the 3.5* installation puts Python on the beginning of the
PATH - whereas I was puttin
Chris Jerdonek added the comment:
I commented above that the tests are not very DRY though. Shouldn't there be
tests to check that the documented behavior is correct?
--
___
Python tracker
<http://bugs.python.org/is
Chris Jerdonek added the comment:
Senthil, in my experience, whenever documentation is added that documents new
aspects of behavior (e.g. is not just a rewording of existing documentation),
tests are always added simultaneously (if not already present) to ensure that
the code doesn't re
Chris Jerdonek added the comment:
> If it would help I could submit a single patch.
Yes, a single patch is best. One way to make code more DRY is refactoring to
use helper functions as needed (i.e. same code in multiple places -> one helper
fu
Chris Jerdonek added the comment:
The number of test cases isn't the problem. Having more but finer-grained test
cases is usually preferred in fact. It's just that the test cases should be
sharing code where possible so that they're shorter and easy to see how they
differ f
Chris Withers added the comment:
Eric, surely this is a bugfix candidate for 3.3.1?
--
___
Python tracker
<http://bugs.python.org/issue17179>
___
___
Python-bug
New submission from Chris Jerdonek:
Currently, unittest's discovery command-line documentation:
http://docs.python.org/dev/library/unittest.html#test-discovery
does not include the long option names (--start-directory, --pattern, and
--top-level-directory):
http://hg.python.org/cpython
New submission from Chris Jerdonek:
Currently, argparser's subparsers.add_parser() method (for adding sub-commands)
takes the following input:
"This object has a single method, add_parser(), which takes a command name and
any ArgumentParser constructor arguments, and returns an Argu
Chris Jerdonek added the comment:
Thanks, one patch should be fine, though the change should be applied to all
branches.
--
___
Python tracker
<http://bugs.python.org/issue17
New submission from Chris Jerdonek:
This issue is to add to argparse's add_mutually_exclusive_group() method
support for passing a title and description. From the argparse docs:
"Note that currently mutually exclusive argument groups do not support the
title and description ar
Chris Withers added the comment:
Some background: I hit this problem when adding Python 3 compatibility
to one of my libraries, where I had the following code:
from types import ClassType
...
class_ = ClassType(n, (sometype, ), dict(class_attr1='foo',
class_attr2='bar'
Chris Jerdonek added the comment:
>> from foo import bar
>> Here bar can be not module, but an attribute of foo (for example, os.path).
> Serhiy: What exception is raised in that situation is controlled by the eval
> loop, not importlib so that would be a separate change.
Ju
Changes by Chris Jerdonek :
--
nosy: +chris.jerdonek
___
Python tracker
<http://bugs.python.org/issue17227>
___
___
Python-bugs-list mailing list
Unsubscribe:
Chris Jerdonek added the comment:
If we can promise not to use it in the from-import case :) I'm okay with the
more specific name (in fact it is preferable). From Brett's response, it
sounds like we have flexibility there and don't need it to be the same? For
from-import I w
Chris Jerdonek added the comment:
> This is not satisfactory. I would prefer:
> import argparse
> argparser = argparse.ArgumentParser()
> subparsers = argparser.add_subparsers('cmd1') % name here
Have you tried passing by keyword?
subparsers = argparser.add_subparsers(des
Changes by Chris Jerdonek :
--
nosy: +bethard, chris.jerdonek
___
Python tracker
<http://bugs.python.org/issue17250>
___
___
Python-bugs-list mailing list
Unsub
Chris Jerdonek added the comment:
I noticed this before and wasn't able to fix it after trying a few things. I
wonder if this is a limitation or bug in Sphinx. At the top, the FAQ page has--
:tocdepth: 2
Levels beyond 2 are getting numbered 25 (the number of the top level) instea
Chris Jerdonek added the comment:
> Levels beyond 2 are getting numbered 25 (the number of the top level) instead
> of having their numbering suppressed (as I would expect it to).
Actually, what I meant to say is that I would expect the "tocdepth" to affect
only the level
Chris Jerdonek added the comment:
Looks like it's because highlightlang:: c is at the top.
--
nosy: +chris.jerdonek
___
Python tracker
<http://bugs.python.org/is
Chris Jerdonek added the comment:
Thanks for waiting and for posting the patches here. I think the second patch
"2-move_two_sections.diff" should be committed now, along with making "Working
with Mercurial" a higher-level header (as it is done in the aggregate patch).
Th
New submission from Chris Jerdonek:
The documentation guidelines in the devguide list a convention for section
headers:
http://docs.python.org/devguide/documenting.html#sections
The current wording, however, can be interpreted to mean that this convention
is always (and should always) be
Chris Jerdonek added the comment:
> It can just be changed to being a suggestion as opposed to "the convention
> that we use."
I created issue 17270 for this.
--
___
Python tracker
<http://bugs.py
Changes by Chris Jerdonek :
--
resolution: -> fixed
stage: commit review -> committed/rejected
status: open -> closed
___
Python tracker
<http://bugs.python.or
Changes by Chris Jerdonek :
--
resolution: -> fixed
stage: needs patch -> committed/rejected
status: open -> closed
___
Python tracker
<http://bugs.python.or
Chris Jerdonek added the comment:
For reasons I stated above, I think it will help to break this issue into
smaller, self-contained parts as we go -- even if some of the issues turn out
to be short-lived.
For example, an issue can be created for adding to the docs a section on how to
set up
Chris Jerdonek added the comment:
> The "Clones setup" section is not about "how to set up a clone", but "how do
> I do these steps depending on the specific setup I'm using" (single or
> multiple clones).
Then the section should be called some
Chris Jerdonek added the comment:
> Adding a patch to fix this issue.
I had tried this, but doesn't this make the contents in the left side bar
unwieldy (and perhaps also on the devguide index page) -- is that what we want?
I was under the assumption that the purpose of the
Chris Withers added the comment:
Barry advised me to open this issue as it's a functional regression from Python
2.
My use case is unit testing code that registers atexit handlers and making sure
the right handlers are registered with the correct param
Chris Withers added the comment:
I can think of other use cases. Anyway, I'm just glad your opinion isn't the
only one there is ;-)
--
___
Python tracker
<http://bugs.python.o
Chris Jerdonek added the comment:
Thanks, Jyrki and Petri. I just noticed that a "Changed in version" should
probably be added at the end of this section:
http://docs.python.org/dev/library/unittest.html#unittest.main
*defaultTest* should probably also be documented in the text (it
Chris Jerdonek added the comment:
I can take care of the Changed in version.
--
___
Python tracker
<http://bugs.python.org/issue15132>
___
___
Python-bugs-list m
New submission from Chris Jerdonek:
This issue is to document the defaultTest parameter to unittest.main():
http://docs.python.org/dev/library/unittest.html#unittest.main
Note that it is not enough simply to say that *defaultTest* is a "default test
name or iterable of test names.&
Chris Jerdonek added the comment:
> *defaultTest* should probably also be documented in the text
I created issue 17282 for this.
--
___
Python tracker
<http://bugs.python.org/issu
Chris Jerdonek added the comment:
FYI, the fix for issue 16403 adds I believe the first mention of PKG-INFO to
the docs (as an aside when discussing the maintainer field). However, a
description of PKG-INFO, etc. should still be added somewhere
Chris Jerdonek added the comment:
I would be happy to commit and watch the buildbots, once I have confidence in
the patch though. Question: I noticed that the following was changed in
Lib/test/regrtest.py:
-with support.temp_cwd(TESTCWD, quiet=True):
+with support.temp_cwd(quiet=True
New submission from Chris Jerdonek:
As discussed here:
http://bugs.python.org/issue15305#msg182853
this issue is for Lib/test/__main__.py to share code with Lib/test/regrtest.py
to minimize duplication of code:
http://hg.python.org/cpython/file/96f08a22f562/Lib/test/regrtest.py#l1594
http
Chris Jerdonek added the comment:
> Those two code chunks should really share code by the way
I created issue 17283 for this (it's okay to fix the current issue before this
one).
--
___
Python tracker
<http://bugs.python.org
New submission from Chris Jerdonek:
As discussed in issue 14468, this issue is to reorder the sections in the
devguide's committing.rst to create a section dedicated to using Mercurial when
committing. The attached patch is adapted from the "2-move_two_sections.diff"
patc
2401 - 2500 of 2758 matches
Mail list logo
