[issue37401] pygrib install error

2019-06-25 Thread Borja 

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/site-packages (from 
pygrib) (1.16.4)
Installing collected packages: pygrib
  Running setup.py install for pygrib ... error
ERROR: Complete output from command /home/python3/bin/python3.7 -u -c 
'import setuptools, 
tokenize;__file__='"'"'/tmp/pip-install-qcxz0945/pygrib/setup.py'"'"';f=getattr(tokenize,
 '"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"', 
'"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' install 
--record /tmp/pip-record-qd474uhl/install-record.txt 
--single-version-externally-managed --compile:
ERROR: /tmp/pip-install-qcxz0945/pygrib/setup.py:41: DeprecationWarning: 
The SafeConfigParser class has been renamed to ConfigParser in Python 3.2. This 
alias will be removed in future versions. Use ConfigParser directly instead.
  config = _ConfigParser()
running install
running build
running build_py
creating build
creating build/lib.linux-x86_64-3.7
copying ncepgrib2.py -> build/lib.linux-x86_64-3.7
running build_ext
building 'pygrib' extension
creating build/temp.linux-x86_64-3.7
gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O3 
-Wall -fPIC -I/home/python3/lib/python3.7/site-packages/numpy/core/include 
-Ig2clib_src -I/home/python3/include/python3.7m -c pygrib.c -o 
build/temp.linux-x86_64-3.7/pygrib.o
In file included from 
/home/python3/lib/python3.7/site-packages/numpy/core/include/numpy/ndarraytypes.h:1822:0,
 from 
/home/python3/lib/python3.7/site-packages/numpy/core/include/numpy/ndarrayobject.h:12,
 from 
/home/python3/lib/python3.7/site-packages/numpy/core/include/numpy/arrayobject.h:4,
 from pygrib.c:613:

/home/python3/lib/python3.7/site-packages/numpy/core/include/numpy/npy_1_7_deprecated_api.h:17:2:
 aviso: #warning "Using deprecated NumPy API, disable it with " "#define 
NPY_NO_DEPRECATED_API NPY_1_7_API_VERSION" [-Wcpp]
 #warning "Using deprecated NumPy API, disable it with " \
  ^
pygrib.c:614:22: error fatal: grib_api.h: No existe el fichero o el 
directorio
 #include "grib_api.h"
  ^
compilación terminada.
error: command 'gcc' failed with exit status 1

ERROR: Command "/home/python3/bin/python3.7 -u -c 'import setuptools, 
tokenize;__file__='"'"'/tmp/pip-install-qcxz0945/pygrib/setup.py'"'"';f=getattr(tokenize,
 '"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"', 
'"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' install 
--record /tmp/pip-record-qd474uhl/install-record.txt 
--single-version-externally-managed --compile" failed with error code 1 in 
/tmp/pip-install-qcxz0945/pygrib/

Numpy (1.16.4)
Python (3.7.3)
Pip (19.1.1)

--
components: Extension Modules
messages: 346520
nosy: Saszalez
priority: normal
severity: normal
status: open
title: pygrib install error
versions: Python 3.7

___
Python tracker 
<https://bugs.python.org/issue37401>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue37415] Error build Python with Intel compiler

2019-06-26 Thread Borja 


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 seen, but when I execute make, the following 
message is printed:

Running code to generate profile data (this can take a while):
# First, we need to create a clean build with profile generation
# enabled.
make profile-gen-stamp
make[1]: se ingresa al directorio `/home/python/source/Python-3.7.3'
Building with support for profile generation:
make build_all_generate_profile
make[2]: se ingresa al directorio `/home/python/source/Python-3.7.3'
make build_all CFLAGS_NODIST=" -prof-gen" LDFLAGS_NODIST=" -prof-gen" 
LIBS="-lcrypt -lpthread -ldl  -lutil"
make[3]: se ingresa al directorio `/home/python/source/Python-3.7.3'
icc -pthread -c -Wsign-compare -Wunreachable-code -DNDEBUG -g  -O3 -Wall
-std=c99 -Wextra -Wno-unused-parameter -Wno-missing-field-initializers 
-Wno-cast-function-type -Werror=implicit-function-declaration -fp-model strict 
-prof-gen  -I. -I./Include-DPy_BUILD_CORE -o Programs/python.o 
./Programs/python.c
icc: command line warning #10006: ignoring unknown option 
'-Wno-cast-function-type'
In file included from ./Include/Python.h(75),
 from ./Programs/python.c(3):
./Include/pyatomic.h(39): error: identifier "atomic_uintptr_t" is undefined
  atomic_uintptr_t _value;
  ^

compilation aborted for ./Programs/python.c (code 2)

--
messages: 346637
nosy: Saszalez
priority: normal
severity: normal
status: open
title: Error build Python with Intel compiler
type: compile error

___
Python tracker 
<https://bugs.python.org/issue37415>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue37415] Error build Python with Intel compiler

2019-06-27 Thread Borja 


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 
<https://bugs.python.org/issue37415>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue37415] Error build Python with Intel compiler: doesn't provide atomic_uintptr_t

2019-06-27 Thread Borja 


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/file48443/stdatomic.h

___
Python tracker 
<https://bugs.python.org/issue37415>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue7897] Support parametrized tests in unittest

2012-07-02 Thread Borja Ruiz Castro 

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:

>
> R. David Murray  added the comment:
>
> People interested in this issue might be interested in changeset
> e6a33938b03f.  I use parameterized unit tests in email a lot, and was
> annoyed by the fact that I couldn't run the tests individually using the
> unittest CLI.  The fix for that turned out to be trivial, but by the time I
> figured it out, I'd already written most of the metaclass.  So since the
> metaclass reduces the boilerplate (albeit at the cost of looking like black
> magic), I decided to go with it.  And the metaclass at least avoids the
> rather questionable use of the "modify locals()" hack I was using before.
>
> --
>
> ___
> Python tracker 
> <http://bugs.python.org/issue7897>
> ___
> ___
> Python-bugs-list mailing list
> Unsubscribe:
> http://mail.python.org/mailman/options/python-bugs-list/isec%40alienvault.com
>
>

--
nosy: +borja.ruiz

___
Python tracker 
<http://bugs.python.org/issue7897>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue7897] Support parametrized tests in unittest

2012-07-02 Thread Borja Ruiz Castro 

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 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:
>
> >
> > R. David Murray  added the comment:
> >
> > People interested in this issue might be interested in changeset
> > e6a33938b03f.  I use parameterized unit tests in email a lot, and was
> > annoyed by the fact that I couldn't run the tests individually using the
> > unittest CLI.  The fix for that turned out to be trivial, but by the
> time I
> > figured it out, I'd already written most of the metaclass.  So since the
> > metaclass reduces the boilerplate (albeit at the cost of looking like
> black
> > magic), I decided to go with it.  And the metaclass at least avoids the
> > rather questionable use of the "modify locals()" hack I was using before.
> >
> > --
> >
> > ___
> > Python tracker 
> > <http://bugs.python.org/issue7897>
> > ___
> > ___
> > Python-bugs-list mailing list
> > Unsubscribe:
> >
> http://mail.python.org/mailman/options/python-bugs-list/isec%40alienvault.com
> >
> >
>
> --
> nosy: +borja.ruiz
>
> ___
> Python tracker 
> <http://bugs.python.org/issue7897>
> ___
>

--

___
Python tracker 
<http://bugs.python.org/issue7897>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com