[issue20677] Minor typo in enum docs
New submission from flashk: On line 142 in the enum library documentation, I believe the text is missing you. It should be changed from: If have an enum member and need its name or value: to: If you have an enum member and need its name or value: -- assignee: docs@python components: Documentation messages: 211536 nosy: docs@python, flashk priority: normal severity: normal status: open title: Minor typo in enum docs type: enhancement versions: Python 3.4 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20677 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10583] Encoding issue with chm help in 2.7.1
flashk fla...@gmail.com added the comment: Yes, I still notice this issue with the 2.7.2 release. As I mentioned earlier, I did not notice this problem with 2.7. Were there any significant changes to the docs between 2.7 and 2.7.1? Considering the bug with HTML Help pointed out by Kristian, I'm thinking there was either a change in the html encoding or the build environment for the Windows installer. Anybody aware of either of these changes happening between 2.7 and 2.7.1? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10583 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10742] memoryview.readonly attribute is not documented
New submission from flashk fla...@gmail.com: The 'readonly' attribute is not explicitly described, even though it is used in the sample code for the memoryview type. I've attached a patch that adds a description of the 'readonly' attribute. -- assignee: d...@python components: Documentation files: stdtypes.diff keywords: patch messages: 124403 nosy: d...@python, flashk priority: normal severity: normal status: open title: memoryview.readonly attribute is not documented versions: Python 2.7 Added file: http://bugs.python.org/file20121/stdtypes.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10742 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10723] Undocumented built-in exceptions
flashk fla...@gmail.com added the comment: I just attached a new patch that explicitly mentions the inheritance of IndentationError and TabError. -- Added file: http://bugs.python.org/file20099/exceptions_2.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10723 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10723] Undocumented built-in exceptions
New submission from flashk fla...@gmail.com: The Built-in Exceptions page of the Python 2.7 documentation is missing descriptions for BufferError, IndentationError, and TabError. I've gone ahead and added a brief description of each error to the page. -- assignee: d...@python components: Documentation files: exceptions.rst messages: 124165 nosy: d...@python, flashk priority: normal severity: normal status: open title: Undocumented built-in exceptions versions: Python 2.7 Added file: http://bugs.python.org/file20084/exceptions.rst ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10723 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10723] Undocumented built-in exceptions
flashk fla...@gmail.com added the comment: Just realized I previously attached the entire file. Here is the diff instead. -- keywords: +patch Added file: http://bugs.python.org/file20085/exceptions.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10723 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10583] Encoding issue with chm help in 2.7.1
New submission from flashk fla...@gmail.com: I just updated to Python 2.7.1 and noticed a small issue with the chm help file. The search results tab displays incorrect characters for various topic titles. It seems to be an encoding issue. For example, searching for 'json' yields the following results: - 18.2 json — JSON encoder and decoder - What’s New in Python 2.6 I noticed this issue on Windows XP 32-bit and Windows 7 64-bit. This issue does not exist with the 2.7 chm file. -- assignee: d...@python components: Documentation, Windows messages: 122857 nosy: d...@python, flashk priority: normal severity: normal status: open title: Encoding issue with chm help in 2.7.1 type: behavior versions: Python 2.7 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10583 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8901] Windows registry path not ignored with -E option
flashk fla...@gmail.com added the comment: Any chance of getting this into 2.7 final? This fix is important for embedding Python in Windows applications. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8901 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8993] Small typo in docs for PySys_SetArgv
New submission from flashk fla...@gmail.com: The docs for PySys_SetArgv say: This function works like PySys_SetArgv() with updatepath set to 1. I believe it should be PySys_SetArgvEx. I've attached a patch. -- assignee: d...@python components: Documentation files: init.rst.patch keywords: patch messages: 107771 nosy: d...@python, flashk priority: normal severity: normal status: open title: Small typo in docs for PySys_SetArgv versions: Python 2.7 Added file: http://bugs.python.org/file17665/init.rst.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8993 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8901] Windows registry path not ignored with -E option
New submission from flashk fla...@gmail.com: Hi, I noticed that Python still uses the Windows registry to initialize sys.path, when the -E option is used. From my understanding, this option is mostly used by programs that are running an embedded version of python, and don't want it to be affected by global installations. Ignoring the registry, along with environment variables, seems to be the correct behavior in this case. I asked about this on the python-dev list (http://mail.python.org/pipermail/python-dev/2010-June/100492.html) and was told to submit a patch for this if I wanted it fixed before the 2.7 release. I've included a patch for 2.7 and 3.2 -- components: Interpreter Core files: IgnoreWindowsRegistry_27.patch keywords: patch messages: 107121 nosy: flashk priority: normal severity: normal status: open title: Windows registry path not ignored with -E option type: behavior versions: Python 2.7, Python 3.2 Added file: http://bugs.python.org/file17558/IgnoreWindowsRegistry_27.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8901 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8901] Windows registry path not ignored with -E option
Changes by flashk fla...@gmail.com: Added file: http://bugs.python.org/file17559/IgnoreWindowsRegistry_32.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8901 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7268] 2to3 execfile conversion changes behavior
New submission from flashk fla...@gmail.com: I recently ran 2to3 on some of my scripts and noticed a change in behavior. I had a script that used the built-in execfile function. After the conversion, it was changed to manually open the file and read the contents into the exec function. Now I am getting a SyntaxError with the modified code. The SyntaxError is caused when the new exec code is called on a script that ends with an empty indented line. I'm not sure if this is an error with the 2to3 script or the built- in exec function. I've attached a very minimal test case. The test.py file is a simple hello world script that ends with an empty indented line. The execfile_example.py file simply calls execfile on the test.py script. The execfile_example_converted.py file is the 2to3 converted version of execfile_example.py. I'm running Python 2.6.2 on Windows XP. -- components: 2to3 (2.x to 3.0 conversion tool), Interpreter Core files: execfile_problem.zip messages: 94949 nosy: flashk severity: normal status: open title: 2to3 execfile conversion changes behavior type: behavior versions: Python 2.6 Added file: http://bugs.python.org/file15267/execfile_problem.zip ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7268 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7268] 2to3 execfile conversion changes behavior
Changes by flashk fla...@gmail.com: Added file: http://bugs.python.org/file15268/test.py ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7268 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7268] 2to3 execfile conversion changes behavior
Changes by flashk fla...@gmail.com: Added file: http://bugs.python.org/file15269/execfile_example.py ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7268 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7268] 2to3 execfile conversion changes behavior
Changes by flashk fla...@gmail.com: Added file: http://bugs.python.org/file15270/execfile_example_converted.py ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7268 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7268] 2to3 execfile conversion changes behavior
flashk fla...@gmail.com added the comment: I just attached the files individually. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7268 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7268] 2to3 execfile conversion changes behavior
flashk fla...@gmail.com added the comment: I'm running this code under 2.6, so the print statement should not be the issue. I've attached a new version of test.py that simply performs a variable assignment and I still get the syntax error on both 2.6 and 3.1 with the exec function. Also, the syntax error is reported on line 3, which is the empty indented line. Sorry for the confusion. -- Added file: http://bugs.python.org/file15271/test.py ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7268 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7268] 2to3 execfile conversion changes behavior
flashk fla...@gmail.com added the comment: Ok, I converted test.py to use Unix style newlines and still get the syntax error on both 2.6 and 3.1. I'm confused as to why execfile works on the file but reading the contents and passing it to exec behaves differently under 2.6. Sorry if I'm just being dense. -- Added file: http://bugs.python.org/file15272/test.py ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7268 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7268] 2to3 execfile conversion changes behavior
flashk fla...@gmail.com added the comment: Ok, but why am I still getting a syntax error in both 2.6 and 3.1 on the file, even after converting the newlines? If I remove the trailing indentation then everything works properly on 2.6 and 3.1, even with DOS newlines. It just seems that exec does not properly handle code that ends with an empty indented line, but execfile handles it correctly. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7268 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7268] 2to3 execfile conversion changes behavior
flashk fla...@gmail.com added the comment:
On Thu, Nov 5, 2009 at 5:48 PM, Benjamin Peterson rep...@bugs.python.orgwrote:
Well, it works for me with the empty newline. Can you isolate the exact
problem?
For me, the exact problem seems to be that exec raises a SyntaxError if the
code contains a trailing indentation. Here's a summary of everything I've
tried:
* test.py runs successfully on 2.6 and 3.1, regardless of line ending style
(LF, CR+LF)
* execfile('test.py') runs successfully on 2.6, regardless of line ending
style
* exec(compile(open('test.py').read(), 'test.py', 'exec')) raises a
SyntaxError on line 3 of test.py under 2.6 and 3.1, regardless of line
ending style.
* Removing the trailing indentation from test.py causes the above code to
succeed under 2.6 and 3.1, regardless of line ending style.
You mentioned that it worked for you with an empty newline. To be clear, the
last line of test.py contains a single tab, with no newline character.
--
Added file: http://bugs.python.org/file15273/unnamed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7268
___div class=gmail_quoteOn Thu, Nov 5, 2009 at 5:48 PM, Benjamin Peterson
span dir=ltrlt;a
href=mailto:rep...@bugs.python.org;rep...@bugs.python.org/agt;/span
wrote:blockquote class=gmail_quote style=margin:0 0 0 .8ex;border-left:1px
#ccc solid;padding-left:1ex;
div class=im
br
/divWell, it works for me with the empty newline. Can you isolate the exact
problem?/blockquotedivbr/divdivFor me, the exact problem seems to be
that exec raises a SyntaxError if the code contains a trailing indentation.
Here#39;s a summary of everything I#39;ve tried:/div
divbr/divdiv * test.py runs successfully on 2.6 and 3.1, regardless of
line ending style (LF, CR+LF)/divdivbr/divdiv *
quot;execfile(#39;test.py#39;)quot; runs successfully on 2.6, regardless of
line ending style/div
divbr/divdiv * quot;exec(compile(open(#39;test.py#39;).read(),
#39;test.py#39;, #39;exec#39;))quot; raises a SyntaxError on line 3 of
test.py under 2.6 and 3.1, regardless of line ending style./divdiv
br
/divdiv * Removing the trailing indentation from test.py causes the above
code to succeed under 2.6 and 3.1, regardless of line ending
style./divdivbr/divdivYou mentioned that it worked for you with an
empty newline. To be clear, the last line of test.py contains a single tab,
with no newline character./div
divbr/divdivbr/divdivbr/divdivbr/divdivbr/div/div
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7268] 2to3 execfile conversion changes behavior
flashk fla...@gmail.com added the comment:
I noticed that calling exec('\t') raises a SyntaxError, so maybe this is
the root of the problem. I manually added a newline character to the end
of the file contents and it fixes the issue for me:
exec(compile(open('test.py').read()+'\n', 'test.py', 'exec'))
So maybe the 2to3 script should automatically do this in order to be
compatible with previous execfile behavior? Or is this a problem with
exec?
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7268
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
