Open rieder opened 6 years ago
I don't think its a big problem since the async are class methods?? (there are other collisions in the code..)
we can maybe gather those here?
we can maybe gather those here?
good idea. I'll rename the issue.
new option for async as keyword argument to function calls (#339 )
FWIW: the use of async
is a definite showstopper for trying to use Amuse with Python 3.7, since it's a reserved keyword as of 3.7.
ok, asyncawait was introduced in 3.5 and 3.6 but 3.7 makes it reserved..so will change
After discussing with Inti, I like the following:
async
function keyword to return_request
.async()
method to .asynchronous()
sounds good to me.
async is fixed (4b48747)
other cases (not specific to python 3):
i think for "object" as used in the interface definitions (define_parameters, define_methods etc ) this can be replaced by "handler" (these instances of amuse.support.interface.HandleParameters etc)
yes, that sounds good.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 28 days if no further activity occurs. Thank you for your contributions.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 28 days if no further activity occurs. Thank you for your contributions.
Describe the bug amuse/rfi/core.py line 126 defines an "async" function. In Python 3.5+, async is a reserved keyword (https://www.python.org/dev/peps/pep-0492/). We may need to rename this function to prevent "invalid syntax" errors.