[issue24955] webbrowser broken on Mac OS X when using the BROWSER variable
Change by Eitan Adler : -- nosy: +eitan.adler ___ Python tracker <https://bugs.python.org/issue24955> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue36596] tarfile module considers anything starting with 512 bytes of zero bytes to be a valid tar file
Change by Eitan Adler : -- nosy: +eitan.adler ___ Python tracker <https://bugs.python.org/issue36596> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue33597] Compact PyGC_Head
Change by Eitan Adler : -- nosy: +eitan.adler ___ Python tracker <https://bugs.python.org/issue33597> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue33657] float addition rounding error
Change by Eitan Adler <li...@eitanadler.com>: -- nosy: +eitan.adler ___ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue33657> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue33648] unused with_c_locale_warning option in configure should be removed
Eitan Adler <li...@eitanadler.com> added the comment: yeah, I was looking at that too. I think someone else modified related files but never ran a regen (or did so with different tooling than I). Even on master, my regen results in changes. -- ___ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue33648> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue33648] unused with_c_locale_warning option in configure should be removed
Change by Eitan Adler <li...@eitanadler.com>: -- keywords: +patch pull_requests: +6752 stage: -> patch review ___ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue33648> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue33648] unused with_c_locale_warning option in configure should be removed
New submission from Eitan Adler <li...@eitanadler.com>: There is an option for --with-c-locale-warning which was turned into a run-time option in eb81795d7d3a8c898fa89a376d63fc3bbfb9a081. The configuration should be cleaned up. -- messages: 317676 nosy: eitan.adler priority: normal severity: normal status: open title: unused with_c_locale_warning option in configure should be removed ___ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue33648> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue33647] Make string.replace accept **kwargs instead of two arguments
Change by Eitan Adler <li...@eitanadler.com>: -- nosy: +eitan.adler ___ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue33647> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue33012] Invalid function cast warnings with gcc 8 for METH_NOARGS
Change by Eitan Adler <li...@eitanadler.com>: -- nosy: +eitan.adler ___ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue33012> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue32911] Doc strings no longer stored in body of AST
Change by Eitan Adler <li...@eitanadler.com>: -- nosy: +eitan.adler ___ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue32911> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue33579] calendar.timegm not always an inverse of time.gmtime
Eitan Adler <li...@eitanadler.com> added the comment: FTR this was entirely self-inflicted: I had a setting which explicitly asked for non-posix gmtime. That said, leaving this open for the same reasons as above. -- ___ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue33579> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue33579] calendar.timegm not always an inverse of time.gmtime
Eitan Adler <li...@eitanadler.com> added the comment: Relevant conversation: https://lists.freebsd.org/pipermail/freebsd-standards/2018-May/003714.html -- ___ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue33579> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue33579] calendar.timegm not always an inverse of time.gmtime
Eitan Adler <li...@eitanadler.com> added the comment: Thanks! I've confirmed this is the case on my system and will be starting a conversation about fixing it. In the meantime I am leaving this bug open since we may want to detect this case in python and correct for it. -- ___ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue33579> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue33579] calendar.timegm not always an inverse of time.gmtime
Change by Eitan Adler <li...@eitanadler.com>: -- components: +Library (Lib) type: -> behavior ___ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue33579> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue33579] calendar.timegm not always an inverse of time.gmtime
New submission from Eitan Adler <li...@eitanadler.com>: How to reproduce: ∴cat bad.py import time import calendar one = time.gmtime(1234567899) two = calendar.timegm(time.gmtime(1234567899)) three = time.gmtime(two) print(one) print(two) print(three) print(one == three) Expected behavior: the functions behave as documented: they are inverses Actual behavior: ∴/srv/src/python/cpython/python bad.py time.struct_time(tm_year=2009, tm_mon=2, tm_mday=13, tm_hour=23, tm_min=31, tm_sec=15, tm_wday=4, tm_yday=44, tm_isdst=0) 1234567875 time.struct_time(tm_year=2009, tm_mon=2, tm_mday=13, tm_hour=23, tm_min=30, tm_sec=51, tm_wday=4, tm_yday=44, tm_isdst=0) False Details: python built from f65e31fee3 under debug mode -- messages: 317111 nosy: eitan.adler priority: normal severity: normal status: open title: calendar.timegm not always an inverse of time.gmtime ___ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue33579> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1294959] Problems with /usr/lib64 builds.
Change by Eitan Adler <li...@eitanadler.com>: -- nosy: +eitan.adler ___ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue1294959> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue33528] os.getentropy support
Eitan Adler <li...@eitanadler.com> added the comment: There are few if any valid reasons to make direct use of the syscall from python code. Portable code would have to reimplement most of the logic from `getentropy` in any case. What you're usecase for the direct syscall? -- ___ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue33528> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue30411] git doesn't support "-C" args under 1.8.5 occurs in configure.ac
Change by Eitan Adler <li...@eitanadler.com>: -- nosy: +eitan.adler ___ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue30411> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue30104] clang 4.0 miscompiles dtoa.c, giving broken float parsing and printing
Change by Eitan Adler <li...@eitanadler.com>: -- nosy: +eitan.adler ___ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue30104> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue33531] test_asyncio: test_subprocess test_stdin_broken_pipe() failure on Travis CI
Change by Eitan Adler <li...@eitanadler.com>: -- nosy: +eitan.adler ___ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue33531> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue33528] os.getentropy support
Change by Eitan Adler <li...@eitanadler.com>: -- nosy: +eitan.adler ___ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue33528> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue33473] build system incorrectly handles CC, CFLAGS, LDFLAGS, and related.
Change by Eitan Adler <li...@eitanadler.com>: -- keywords: +patch pull_requests: +6563 stage: -> patch review ___ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue33473> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13590] extension module builds fail with python.org OS X installers on OS X 10.7 and 10.6 with Xcode 4.2
Change by Eitan Adler <li...@eitanadler.com>: -- nosy: +eitan.adler ___ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue13590> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue5755] "-Wstrict-prototypes" is valid for Ada/C/ObjC but not for C++"
Eitan Adler <li...@eitanadler.com> added the comment: copying and adapting my comments on the PR: Strict Prototypes is correct and helpful for C. That said, the way it is currently implemented, by checking for the compiler in CC is sub-optimal at best. CC ought to always be a C compiler, and never a C++ compiler. It also seems questionable that distutils is using the python cflags rather than a dedicated set. The best fix is a separate and specific list of flags for distutils rather than modifying the set of flags used to build python. That said, the current implementing of flags for python isn't great, so lets remove it as a short term fix. -- ___ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue5755> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9031] distutils uses invalid "-Wstrict-prototypes" flag when compiling C++ extension module
Change by Eitan Adler <li...@eitanadler.com>: -- nosy: +eitan.adler ___ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue9031> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue5755] "-Wstrict-prototypes" is valid for Ada/C/ObjC but not for C++"
Change by Eitan Adler <li...@eitanadler.com>: -- nosy: +eitan.adler ___ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue5755> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1222585] C++ compilation support for distutils
Change by Eitan Adler <li...@eitanadler.com>: -- nosy: +eitan.adler ___ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue1222585> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue33484] build system runs when it may merely link
Change by Eitan Adler <li...@eitanadler.com>: -- title: build system runs when it merely link -> build system runs when it may merely link ___ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue33484> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue33486] regen autotools related files
Change by Eitan Adler <li...@eitanadler.com>: -- pull_requests: +6528 ___ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue33486> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue33486] regen autotools related files
Eitan Adler <li...@eitanadler.com> added the comment: > If these changes are autogenerated, I would prefer that a trusted core > developer create a PR. They are fully auto-generated (using autoupdate and autoreconf). It someone else wants to submit the PR, feel free. > Is it safe to bump the minimal required version of autotools to 2.69? This > can prevent building Python on conservative systems. This should only affect rerunning autoreconf and related tools. It won't affect the use of "configure" (and therefore "make") which is checked into the repository. -- ___ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue33486> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue33512] use more standard approach for detecting long double in configure
Change by Eitan Adler <li...@eitanadler.com>: -- keywords: +patch pull_requests: +6527 stage: -> patch review ___ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue33512> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue33512] use more standard approach for detecting long double in configure
New submission from Eitan Adler <li...@eitanadler.com>: autotools has a standard macro for defining HAVE_LONG_DOUBLE. Lets use it rather than using our own. -- components: Build messages: 316615 nosy: eitan.adler priority: normal severity: normal status: open title: use more standard approach for detecting long double in configure ___ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue33512> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue33511] update.config.sub
Change by Eitan Adler <li...@eitanadler.com>: -- keywords: +patch pull_requests: +6525 stage: -> patch review ___ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue33511> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue33511] update.config.sub
New submission from Eitan Adler <li...@eitanadler.com>: confg.sub has been updated upstream. lets pull it in. -- components: Build messages: 316612 nosy: eitan.adler priority: normal severity: normal status: open title: update.config.sub type: enhancement ___ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue33511> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue33483] build system requires explicit compiler, but should discover it
Eitan Adler <li...@eitanadler.com> added the comment: On any system where "gcc" is not the correct compiler to use. If it does not exist, is too old, points to the incorrect compiler, etc. Concretely I have two such systems: - on one, "gcc" does not exist - on the other "gcc" is actually a hardlink to "clang" -- ___ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue33483> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue33490] pthread auto-detection can use AX_PTHREAD
New submission from Eitan Adler <li...@eitanadler.com>: There is a ton of logic in configure.ac to detect pthreads support. There is a standard macro to use instead: https://www.gnu.org/software/autoconf-archive/ax_pthread.html#ax_pthread In order to simplify our pthread logic we should make use of the standard macro instead of writing our own code. -- components: Build messages: 316491 nosy: eitan.adler priority: normal severity: normal status: open title: pthread auto-detection can use AX_PTHREAD type: enhancement ___ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue33490> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue33490] pthread auto-detection can use AX_PTHREAD
Change by Eitan Adler <li...@eitanadler.com>: -- keywords: +patch pull_requests: +6475 stage: -> patch review ___ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue33490> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue33488] github pull request template does not satisfy markdownlint
Change by Eitan Adler <li...@eitanadler.com>: -- keywords: +patch pull_requests: +6473 stage: -> patch review ___ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue33488> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue33488] github pull request template does not satisfy markdownlint
New submission from Eitan Adler <li...@eitanadler.com>: markdownlint is, as the name implies, a tool for linting markdown files. The current template has the following lint warnings: ``` ./.github/PULL_REQUEST_TEMPLATE.md:8: MD031 Fenced code blocks should be surrounded by blank lines ./.github/PULL_REQUEST_TEMPLATE.md:10: MD031 Fenced code blocks should be surrounded by blank lines ./.github/PULL_REQUEST_TEMPLATE.md:19: MD031 Fenced code blocks should be surrounded by blank lines ./.github/PULL_REQUEST_TEMPLATE.md:21: MD031 Fenced code blocks should be surrounded by blank lines ``` These should be fixed -- assignee: docs@python components: Documentation messages: 316484 nosy: docs@python, eitan.adler priority: normal severity: normal status: open title: github pull request template does not satisfy markdownlint type: enhancement ___ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue33488> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue33486] regen autotools related files
Change by Eitan Adler <li...@eitanadler.com>: -- keywords: +patch pull_requests: +6470 stage: -> patch review ___ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue33486> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue33486] regen autotools related files
New submission from Eitan Adler <li...@eitanadler.com>: There are few if any functional changes, but this is helpful when making other changes to the build system. -- components: Build messages: 316477 nosy: eitan.adler priority: normal severity: normal status: open title: regen autotools related files type: enhancement ___ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue33486> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue33484] build system runs when it merely link
Eitan Adler <li...@eitanadler.com> added the comment: I believe I have removed the regen step from all my patches. I will separately upgrade the generated files (particularly since it is only a minor version bump). -- ___ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue33484> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue33485] autoconf target does not behave correctly
Change by Eitan Adler <li...@eitanadler.com>: -- keywords: +patch pull_requests: +6469 stage: -> patch review ___ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue33485> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue33484] build system runs when it merely link
Eitan Adler <li...@eitanadler.com> added the comment: The unrelated changes are likely due to the "regen" step. I am using newer tools than previously used. It is unclear to me why we include generated files in the repository. Some projects prefer this to avoid the need to have autotools installed on the build machine. With regard to "some cases where we really do have to *run* the code to prove the function" you will notice that this is not a complete search and replace: I manually looked through the various uses of AC_RUN_IFELSE and only changed the ones that I thought should be changed. If someone has more knowledge of more arcane platforms and disagrees with my assessment, I will happily revert those changes. -- ___ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue33484> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue33485] autoconf target does not
New submission from Eitan Adler <li...@eitanadler.com>: The current "autoconf" target is suboptimal in a few ways: - it does not use a quoted srcdir - it uses autoheader and autoconf instead of autoreconf - it does act sanely if 'cd' fails. -- components: Build messages: 316472 nosy: eitan.adler priority: normal severity: normal status: open title: autoconf target does not type: behavior ___ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue33485> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue33485] autoconf target does not behave correctly
Change by Eitan Adler <li...@eitanadler.com>: -- title: autoconf target does not -> autoconf target does not behave correctly ___ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue33485> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue33484] build system runs when it merely link
Change by Eitan Adler <li...@eitanadler.com>: -- keywords: +patch pull_requests: +6468 stage: -> patch review ___ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue33484> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue33484] build system runs when it merely link
New submission from Eitan Adler <li...@eitanadler.com>: The build system attempts to run certain test code when it can actually just link the code. This is a minor performance optimization but is really a semantic correctness issue. -- components: Build messages: 316471 nosy: eitan.adler priority: normal severity: normal status: open title: build system runs when it merely link ___ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue33484> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue33483] build system requires explicit compiler, but should discover it
Change by Eitan Adler <li...@eitanadler.com>: -- keywords: +patch pull_requests: +6466 stage: -> patch review ___ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue33483> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue33483] build system requires explicit compiler, but should discover it
New submission from Eitan Adler <li...@eitanadler.com>: configure.ac requires explicit configuration for finding the preferred compiler. This results in a non-native way of configuring the system, and does not actually work on most platforms. Expected behavior: CC is used to discover the C compiler; CPP, LD, CXX, etc. are used to discover their appropriate tools Actual: --without-gcc or --with-icc must be explicitly passed -- components: Build messages: 316468 nosy: eitan.adler priority: normal severity: normal status: open title: build system requires explicit compiler, but should discover it type: compile error ___ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue33483> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue33473] build system incorrectly handles CC, CFLAGS, LDFLAGS, and related.
New submission from Eitan Adler <li...@eitanadler.com>: There are a number of incorrect items in python's build system. Expected behavior: - CC is correctly report as the compiler, and without any additional options - CFLAGS is correctly reported for the required flags to the compiler - CXXFLAGS is the same as CFLAGS, but for C++ - LDFLAGS is correctly report for linker flags Actual behavior: - CC is reported as a non-existing compiler plus an option - C*FLAGS and LDFLAGS are not correctly reported -- components: Build messages: 316431 nosy: eitan.adler priority: normal pull_requests: 6459 severity: normal status: open title: build system incorrectly handles CC, CFLAGS, LDFLAGS, and related. type: compile error ___ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue33473> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue33472] build system incorrectly handles CC, CFLAGS, LDFLAGS, and related.
Eitan Adler (bad account) <eitan+bo...@eitanadler.com)> added the comment: closing this as I created under a bad account and can't find a way to merge them. -- resolution: -> duplicate stage: -> resolved status: open -> closed ___ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue33472> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue33472] build system incorrectly handles CC, CFLAGS, LDFLAGS, and related.
New submission from Eitan Adler <ei...@eitanadler.com>: There are a number of incorrect items in python's build system. Expected behavior: - CC is correctly report as the compiler, and without any additional options - CFLAGS is correctly reported for the required flags to the compiler - CXXFLAGS is the same as CFLAGS, but for C++ - LDFLAGS is correctly report for linker flags Actual behavior: - CC is reported as a non-existing compiler plus an option - C*FLAGS and LDFLAGS are not correctly reported -- components: Build messages: 316429 nosy: Eitan Adler priority: normal pull_requests: 6458 severity: normal status: open title: build system incorrectly handles CC, CFLAGS, LDFLAGS, and related. type: compile error ___ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue33472> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue20353] Hanging bug with multiprocessing + sqlite3 + tkinter (OS X 10.9 only)
Change by Eitan Adler <li...@eitanadler.com>: -- nosy: +eadler ___ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue20353> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13829] exception error in _scproxy.so when called after fork
Change by Eitan Adler <li...@eitanadler.com>: -- nosy: +eadler ___ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue13829> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue27126] Apple-supplied libsqlite3 on OS X is not fork safe; can cause crashes
Change by Eitan Adler <li...@eitanadler.com>: -- nosy: +eadler ___ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue27126> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue16605] test_posix.test_fs_holes() fails on FreeBSD 9.0
Changes by Eitan Adler li...@eitanadler.com: -- nosy: +eadler ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16605 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
