Borja added the comment:
Two things.
I searched a bit more and found "atomic_uint" inside , but it's
not exactly the same as what you wrote.
What you have put me to try, where do I put it?
I attached in case it helps.
--
Added file: https://bugs.python.org/file48
Borja added the comment:
In pyconfig.h the variable HAVE_STD_ATOMIC appears like this:
/* Has stdatomic.h with atomic_int */
#define HAVE_STD_ATOMIC 1
I searched at atomic_uintptr_t and found nothing.
--
___
Python tracker
<ht
New submission from Borja :
I'm trying to build Python 3.7 on CentOS 7 with Intel compilers. To compile I
do the following:
export CC=icc
export CXX=icpc
export FC=ifort
./configure --prefix=my_prefix --enable-optimizations --without-gcc
make
make install
In the configure, no error is
New submission from Borja :
Installing Pygrib with pip (pip install pygrib):
Collecting pygrib
Using cached
https://files.pythonhosted.org/packages/f8/10/c0d22eafec62fb5413799a7034ac45f26bfa77405c8527c17869e4c3ee4d/pygrib-2.0.4.tar.gz
Requirement already satisfied: numpy in ./lib/python3.7
Borja Ruiz Castro added the comment:
Sorry, I failed to mention that I use Testify to launch all my tests!
On 2 July 2012 13:23, Borja Ruiz Castro wrote:
>
> Borja Ruiz Castro added the comment:
>
> Hi Murray!
>
> I use a lot od parametrized tests. I usually use the
Borja Ruiz Castro added the comment:
Hi Murray!
I use a lot od parametrized tests. I usually use the ENV to pass these
parameters and/or a custon configuration file.
What is your approach to parametrize all the test stuff?
Regards,
Borja.
On 31 May 2012 03:57, R. David Murray wrote