You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a MUSIC-aware application, NEST controls MUSIC. For example, it controls when switching to the Runtime phase and it calls the MUSIC tick() in its simulation loop.
By importing the MUSIC Python bindings, you indicate that you intend to do something similar.
Please explain what it is that you want to do in this script. If it is something reasonable, we might be able to provide novel MUSIC support for it.
I would like to import a module I wrote that has *also* some NEST-related
functionality, and therefore in turn imports nest. I cannot import my
module though because I run into the indicated issue.
Best
Cristiano
On Tue, Mar 23, 2021 at 7:11 PM mdjurfeldt ***@***.***> wrote:
Right, but this is, at least almost, a feature.
As a MUSIC-aware application, NEST controls MUSIC. For example, it
controls when switching to the Runtime phase and it calls the MUSIC tick()
in its simulation loop.
By importing the MUSIC Python bindings, you indicate that you intend to do
something similar.
Please explain what it is that you want to do in this script. If it is
something reasonable, we might be able to provide novel MUSIC support for
it.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#70 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AJNSRLAGGGFLJIWCC5FKXLDTFDKWBANCNFSM4ZVVCWQQ>
.
Hi all,
I recently found this issue. If nest is imported, music.Setup() complains that Setup constructor was already called.
running this simple code throws the error:
This is independent of the order of the two imports, and the issue disappears by commenting out
import nest
.The text was updated successfully, but these errors were encountered: