I just found an unexpected behavior and I'm wondering if it is a bug.
In my 2.7.2 interpreter on OS X, built and installed via MacPorts, it
appears that integers are not correctly overflowing into longs and
instead are yielding bizarre results. I can only reproduce this when
using the exponent operator with two ints (declaring either operand
explicitly as long prevents the behavior).
To confirm I'm not crazy, I tried in the 2.7.1 and 2.6.7 installations
included in OS X 10.7, and also a 2.7.2+ (not sure what the + is) on
an Ubuntu machine and didn't see this behavior. This looks like some
kind of truncation error, but I don't know much about the internals of
Python and have no idea what's going on. I assume since it's only in
my MacPorts installation, it must be build configuration issue that is
specific to OS X, perhaps only 10.7, or MacPorts.
Am I doing something wrong, and is there a way to fix it before I
compile? I could find any references to this problem as a known issue.
There are currently a bunch of various buildbot failures on all 3
branches. I would remind committers to regularly take a look at the
buildbots, so that these failures get solved reasonably fast.
I just started getting errors in my PEP 404 / pythonv branch, but they don't
at first glance appear related to the functionality of this branch. What I'm
seeing is that during installation, some of the .pyc/.pyo files written by
compileall have mode 600 rather than the expected 644, with the result that
test_compileall fails when run from the installed Python as an unprivileged
user. If I manually do
sudo chmod a+r /usr/local/lib/python3.3/__pycache__/*
then test_compileall works again.
I added a diagnostic to compileall.py, here's an extract from the log of the
Mode of [...]/__pycache__/__future__.cpython-33.pyc is 644
Mode of [...]/__pycache__/__phello__.foo.cpython-33.pyc is 644
Mode of [...]/__pycache__/_compat_pickle.cpython-33.pyc is 644
Mode of [...]/__pycache__/_dummy_thread.cpython-33.pyc is 644
Mode of [...]/__pycache__/_markupbase.cpython-33.pyc is 644
Mode of [...]/__pycache__/_pyio.cpython-33.pyc is 644
Mode of [...]/__pycache__/_strptime.cpython-33.pyc is 644
Mode of [...]/__pycache__/_sysconfigdata.cpython-33.pyc is 600
Mode of [...]/__pycache__/_threading_local.cpython-33.pyc is 644
Mode of [...]/__pycache__/_weakrefset.cpython-33.pyc is 600
Mode of [...]/__pycache__/abc.cpython-33.pyc is 600
Mode of [...]/__pycache__/aifc.cpython-33.pyc is 644
The 600s and 644s are interspersed with no pattern immediately apparent. All
the source files have mode 644, as expected.
This happens on two different Posix machines - Ubuntu Natty and OS X Leopard
- so doesn't seem to be related to the external environment.
Can anyone shed any light as to what might be going on?
I am being forced to support multiple versions of python on Windows
platforms. I have been using PEP 397 and the execution of *.py files works
great. Thank you!!
My problem is idle. The various versions of idle have the same problem as
the various versions of python. We were using an editor that allowed python
selection, however, they stopped supporting python and we are back using
idle. Any suggestions on switching versions of idle would be appreciated.