| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
Also added several regression tests.
|
| | |
|
| |
|
|
|
|
| |
Use 'srcdir' from sysconfig instead of 'projectbase' to build a
path to the Tools directory. 'projectbase' is the path of the build
directory, not the source directory.
|
| |
|
|
| |
just assertTrue.
|
| |
|
|
|
|
|
|
|
| |
The gdb hooks for debugging CPython (within Tools/gdb) have
been enhanced to show information on more C frames relevant to CPython within
the "py-bt" and "py-bt-full" commands:
* C frames that are waiting on the GIL
* C frames that are garbage-collecting
* C frames that are due to the invocation of a PyCFunction
|
| |\
| |
| |
| | |
(helps getting results in real-time when stdio is transmitted over a pipe or socket)
|
| | |
| |
| |
| | |
(helps getting results in real-time when stdio is transmitted over a pipe or socket)
|
| | | |
|
| | |
| |
| |
| | |
purpose
|
| |\ \
| |/
| |
| |
| |
| | |
pickle module.
Patch by Stefan Mihaila.
|
| | |
| |
| |
| |
| |
| | |
pickle module.
Patch by Stefan Mihaila.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
python executable
The __os_install_macro defines some post-processing activities during an rpm
build; one of the scripts it calls is brp-python-bytecompile, which can take
an argument: the python executable with which to byte-compile .py files in the
package payload.
In some older versions of rpm (e.g. in RHEL 6), this invocation doesn't pass
in an argument, and brp-python-bytecompile defaults to using /usr/bin/python,
which can lead to the .py files being byte-compiled for the wrong version of
python. This has been fixed in later versions of rpm by passing in
%{__python} as an argument to brp-python-bytecompile.
Workaround this by detecting if __os_install_post has a 0-argument invocation
of brp-python-bytecompile, and if so generating an equivalent macro that has
the argument, and explicitly provide the new definition within the specfile.
|
| | | |
|
| | |
| |
| |
| | |
some systems.
|
| | | |
|
| | |
| |
| |
| | |
behind.
|
| |\ \
| |/ |
|
| | |
| |
| |
| | |
for the patch.
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
python executable
The __os_install_macro defines some post-processing activities during an rpm
build; one of the scripts it calls is brp-python-bytecompile, which can take
an argument: the python executable with which to byte-compile .py files in the
package payload.
In some older versions of rpm (e.g. in RHEL 6), this invocation doesn't pass
in an argument, and brp-python-bytecompile defaults to using /usr/bin/python,
which can lead to the .py files being byte-compiled for the wrong version of
python. This has been fixed in later versions of rpm by passing in
%{__python} as an argument to brp-python-bytecompile.
Workaround this by detecting if __os_install_post has a 0-argument invocation
of brp-python-bytecompile, and if so generating an equivalent macro that has
the argument, and explicitly provide the new definition within the specfile.
|
| | | |
|
| | |
| |
| |
| | |
for SEEK_HOLE/SEEK_DATA
|
| | |
| |
| |
| | |
of os.listdir().
|
| | | |
|
| |\ \
| |/
| |
| |
| |
| |
| |
| | |
to using signal.alarm(1) instead of signal.setitimer(signal.ITIMER_REAL, 0.1).
This is an attempt to see if this change is what caused the ubuntu arm buildbot
to hang in test_io's test_interrupted_write_retry_text.
Discussion in Issue #12268.
|
| | |
| |
| |
| |
| |
| |
| |
| | |
to using signal.alarm(1) instead of signal.setitimer(signal.ITIMER_REAL, 0.1).
This is an attempt to see if this change is what caused the ubuntu arm buildbot
to hang in test_io's test_interrupted_write_retry_text.
Discussion in Issue #12268.
|
| | | |
|
| | | |
|
| | |
| |
| |
| | |
to modules of the same name.
|
| | |
| |
| |
| | |
plain tuple to a collections.namedtuple.
|
| | | |
|
| | | |
|
| | | |
|
| |\ \
| |/ |
|
| | | |
|
| | | |
|
| | | |
|
| |\ \ |
|
| | | | |
|
| |/ /
| |
| |
| | |
interface (yet).
|
| | |
| |
| |
| | |
use "interactive" instead.
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| | |
plain tuples to immutable iterable objects with named attributes
(structseq objects).
|
| | |
| |
| |
| | |
pathconf().
|
| | |
| |
| |
| | |
with a negative hash.
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This code passes all the same tests that the existing RFC mime header
parser passes, plus a bunch of additional ones.
There are a couple of commented out tests where there are issues with the
folding. The folding doesn't normally get invoked for headers parsed from
source, and the cases are marginal anyway (headers with invalid binary data)
so I'm not worried about them, but will fix them after the beta.
There are things that can be done to make this API even more convenient, but I
think this is a solid foundation worth having. And the parser is a full RFC
parser, so it handles cases that the current parser doesn't. (There are also
probably cases where it fails when the current parser doesn't, but I haven't
found them yet ;)
Oh, yeah, and there are some really ugly bits in the parser for handling some
'postel' cases that are unfortunately common.
I hope/plan to to eventually refactor a lot of the code in the parser which
should reduce the line count...but there is no escaping the fact that the
error recovery is welter of special cases.
|
| | | |
|
