Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Switch to using nengo-bones #175

Open
arvoelke opened this issue Apr 17, 2019 · 2 comments
Open

Switch to using nengo-bones #175

arvoelke opened this issue Apr 17, 2019 · 2 comments
Labels
meta

Comments

@arvoelke
Copy link
Owner

arvoelke commented Apr 17, 2019 •
edited
Loading

Supersedes #163, #140.
@arvoelke arvoelke added the meta label Apr 17, 2019
This was referenced Apr 17, 2019
Closed
Closed
Open
@arvoelke
Copy link
Owner Author

arvoelke commented May 9, 2019

Planning to do this following the merge and release of nengo/nengo-bones#17 :)

@arvoelke
Copy link
Owner Author

arvoelke commented Jun 4, 2019

Since nengo-bones is only compatible with Python>3, this would involve dropping support for py2. IMO it would make more sense to wait until we plan to support nengo>=3.0.0, and then do a nengolib=1.0.0 release with all of these changes.

@arvoelke arvoelke mentioned this issue Jun 13, 2019
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
meta
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@arvoelke