Hello,
I'm wondering if set'ing an asyncio.Event guarantees to notify all tasks that
are waiting for the event ?
Thus even if I `set()` the event and directly `clear()` the event, considering
that both thus instructions are no co-routines and thus will not return control
to the event-loop,
it will never call MPI_Init.
I would like to know how other parallel python projects handle this.
Thanks in advance,
Toon Knapen
--
http://mail.python.org/mailman/listinfo/python-list
[EMAIL PROTECTED] wrote:
Toon But some other (but 'similar') functionality is broken. Now I
Toon succeeded in compiling python. But when using distutils (e.g. when
Toon installing numarray using the setup.py), python will compile the
Toon files using the '-xarch=v9' option but
[EMAIL PROTECTED] wrote:
It shouldn't actually be required. I'm assuming the problem is while
trying to run asdlgen.py. The generated files are checked in, but the
timestamps are wrong and the Makefile is trying to be helpful.
Try:
touch Include/Python-ast.h Python/Python-ast.c
To configure python on a Solaris 9 box with sunstudio11 installed and to
compile it in 64bit, I execute following:
code
export CC=cc
export CFLAGS=-xarch=v9
export CXX=CC
export CXXFLAGS=-xarch=v9
export F77=f77
export FFLAGS=-xarch=v9
export LDFLAGS=-xarch=v9
./configure
/code
When doing
[EMAIL PROTECTED] wrote:
I agree, the Python configure/Makefile combination doesn't conform very well
to current GNU style in this regard. Try setting EXTRA_CFLAGS instead of
CFLAGS.
Thanks.
But some other (but 'similar') functionality is broken. Now I succeeded
in compiling python. But
I'm trying to build the svn-trunk version of python on a Solaris box.
However I do not have a python installed yet and apparantly the build of
python requires a python to be accessible (as also annotated in the
Makefile generated during the ./configure). How can I solve this situation?
Thanks,
