Chris Hogan added the comment:
I should be able to try it out today or tomorrow. I'll let you know.
--
___
Python tracker
<http://bugs.python.org/is
Chris Hogan added the comment:
Zach,
3.x had the desired behavior. We didn't have to make any changes.
--
___
Python tracker
<http://bugs.python.org/is
Chris Hogan added the comment:
The Intel compiler team is looking into this issue. I'll keep everyone updated
here.
--
___
Python tracker
<http://bugs.python.org/is
Changes by Chris Hogan :
--
resolution: not a bug ->
status: closed -> open
___
Python tracker
<http://bugs.python.org/issue25589>
___
___
Python-bugs-list
Chris Hogan added the comment:
I guess since no one can reproduce the error, it must be a problem with how I'm
building it. We build our own dependencies (zlib, bzip, sqlite3, openssl,
etc.) with the Intel compiler, so it could be any number of things causing the
issue. Closing as not
Chris Hogan added the comment:
Ned, the test is in Lib/test/test_ascii_formatd.py. Sorry, I spelled it wrong
originally. Also, I guess it's only in 2.7. My mistake.
--
versions: -Python 3.5
___
Python tracker
<http://bugs.python.org/is
New submission from Chris Hogan:
I successfully built Python on OS X 10.10 with the Intel compiler v15.
However, running the regression tests gives me a "segmentation fault: 11" on
test_ascii_formated. I think this has to do with libffi, because when I build
with the --use-syste
Changes by Chris Hogan :
Added file: http://bugs.python.org/file40309/addcflags2_7.patch
___
Python tracker
<http://bugs.python.org/issue24973>
___
___
Python-bugs-list m
New submission from Chris Hogan:
This Visual Studio project change appends to the compiler flags any values in
the CFLAGS environment variable.
--
components: Build, Windows
files: addcflags3_5.patch
keywords: patch
messages: 249427
nosy: christopher.hogan, paul.moore, r.david.murray
New submission from Chris Hogan:
Setup.py evaluates what's given in LDFLAGS and CPPFLAGS and CFLAGS. These
variables are the usual mechanism to communicate custom paths/libs/defs to a
build process. However, setup.py puts system paths in front of custom paths
which makes it impossible t
Chris Hogan added the comment:
I think ensure_relative is incorrect. The comment in the function states:
"Take the full path 'path', and make it a relative path. This is useful to
make 'path' the second argument to os.path.join()."
However, according to t
Chris Hogan added the comment:
Here's a change that might fix the trailing backslash problem for now without
breaking anything. libpath-fix.patch only affects arguments that we know are
paths. This happens before anything is quoted.
This avoids the problem when something like 'C:
Chris Hogan added the comment:
> Since issue 8972 has been resolved by fixing the broken behavior, I think we
> should just use list2cmdline.
> We could leave _nt_quote_args alone and replace the call to it in _spawn_nt
> with:
> cmd = [list2cmdline([arg]) for arg in cmd]
Changes by Chris Hogan :
Added file: http://bugs.python.org/file40205/quote-args-ext.tar.gz
___
Python tracker
<http://bugs.python.org/issue8987>
___
___
Python-bug
Chris Hogan added the comment:
At Intel, we've run into problems with external modules giving paths to
_nt_quote_args that contain trailing backslashes, which escapes the final quote
and breaks the command. This fix takes care of special characters, trailing
backslashes, and embedded q
Chris Hogan added the comment:
>From Clark Nelson:
> In my opinion, exactly how and where the macro is defined that indicates our
> conformance to the FP standard
> doesn't really matter. The point is that it is our intention to conform, at
> least to some degr
Chris Hogan added the comment:
Producing NaN by Py_HUGE_VAL / Py_HUGE_VAL as in the suggested patch is unsafe
as it can generate a FP exception during runtime. Also aggresive compiler FP
optimizations can eliminate this calculation on compile-time. For this reason,
we've used con
17 matches
Mail list logo
