Eric Snow added the comment:
Fair enough.
--
resolution: - not a bug
stage: needs patch - resolved
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue24370
___
Steve Dower added the comment:
I need to see the detailed log to be any more helpful. Can you try running this
command and post the log here:
msiexec /l*vx log.txt /x {9529565F-E693-3F11-B3BF-8CD545F5F9A0}
(Note that the UUID is different from earlier because it matches 3.4.3.amd64
and the
Peter Eastman added the comment:
I don't believe that explanation is correct. You can just as easily get the
same problem without explicitly passing a map to exec(). For example:
def f():
script =
print(a)
print([a for i in range(5)])
a = 5
exec(script)
f()
The
R. David Murray added the comment:
Yes it is. The comprehension is a *new* scope, within the outer scope of the
exec, and it *cannot see* the variables in the outer scope of the exec. You
have the same problem if you try to use a comprehension in that way in a class
statement at the class
Peter Eastman added the comment:
Then fix the documentation. This behavior directly contradicts the
documentation of the exec() function. The question is not what scope the
comprehension runs in, it's what scope the script runs in. See my third
example. A comprehension in the f() function
Ethan Henderson added the comment:
Running that in my command prompt outputs Access is denied, even after
disabling UAC.
Running that in bash just gives me a popup for Windows Installer.
Is the UUID going to be different for 3.4.3 intel x64 (I have intel, not amd)?
--
R. David Murray added the comment:
OK, it looks like what the documentation of exec is missing is the fact that
calling exec with no arguments in a non-global is equivalent to calling it with
*two* arguments. That is, your exec(script) statement is equivalent to
exec(script, globals(),
Changes by R. David Murray rdmur...@bitdance.com:
--
versions: +Python 3.5, Python 3.6
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue24800
___
___
Changes by Yury Selivanov yseliva...@gmail.com:
--
nosy: +yselivanov
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue24667
___
___
Python-bugs-list
Steve Dower added the comment:
Start from an elevated command prompt. There's only one 64-bit build, so
that'll be it. Our name for it is amd64, even though it applies to both Intel
and AMD.
--
___
Python tracker rep...@bugs.python.org
Mark Roseman added the comment:
I'd like to revisit this, particularly in the context of some of the
discussions regarding future improvements of IDLE.
Assume we have a barebones Tcl/Tk framework build of e.g. 8.6.4 as part of the
installer (core Tcl/Tk, not like e.g. ActiveTcl).
Would
Roundup Robot added the comment:
New changeset e4cb64628673 by Yury Selivanov in branch '3.5':
Issue #24791: Fix grammar regression for call syntax: 'g(*a or b)'.
https://hg.python.org/cpython/rev/e4cb64628673
New changeset 4c89dd5199e5 by Yury Selivanov in branch 'default':
Merge 3.5 (issue
Roundup Robot added the comment:
New changeset 40c391d12741 by Yury Selivanov in branch '3.5':
Issue #24791: More tests in test_parser
https://hg.python.org/cpython/rev/40c391d12741
New changeset a572137b4f05 by Yury Selivanov in branch 'default':
Merge 3.5 (issue #24791; more tests in
Changes by Yury Selivanov yseliva...@gmail.com:
--
resolution: - fixed
stage: needs patch - resolved
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue24791
___
Robert Collins added the comment:
So, I think the majority opinion seems to be:
module.type at address value1, value2, ...
AIUI the patch doesn't quite do that, so I'm going to pop this back to patch
review.
That said, Serhiy, if you fix it up, just commit it please :)
--
nosy:
Ethan Henderson added the comment:
My log.txt: http://puu.sh/jqLWR.txt
Turns out that my antivirus was blocking that command from running before.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22329
Martin Panter added the comment:
I’m a bit confused. In the current patch, the new type_str() function appears
to use the “qualname” (which I support), but some of the test changes seem to
contradict this, e.g.:
C.foo(1)
-classmethod class 'test.test_descrtut.C' 1
+classmethod C 1
Also, I
Martin Panter added the comment:
In my experience, I tend to only use memoryview() for “bytes-like” buffers (but
see Issue 23756 about clarifying what this means). Example from
/Lib/_compression.py:67:
def readinto(self, b):
with memoryview(b) as view, view.cast(B) as byte_view:
Martin Panter added the comment:
From what I can see, the examples in the current documentation tend to diectly
call loop.close() without an exception handler. Only two examples have the
bare-bones try / finally handler (which is important for the example that uses
Ctrl+C).
--
nosy:
101 - 119 of 119 matches
Mail list logo