Macintosh conflict with numpy

[ChrisHuyck]

I've got a student working with pyNN and nest on a macintosh. We can install pynn and nest, but running a simulation fails if there is more than one neuron. It says that np.bool is deprecated in numpy. It seems we have numpy 1.24.1 installed, where bool has been actually removed from numpy. bool is in numpy 1.23.1 but it's not compatible with python3.11, which is what we use to get nest and pyNN to work together. I looked through the issues and couldn't see a mac tag. Does anyone have a solution?

[apdavison]

Hi Chris,

I believe this problem has been fixed in the master branch. We're planning to make a release sometime in the next two weeks. If you can't wait that long, please try to install PyNN from the master branch.

[ChrisHuyck]

That doesn't seem to work for me (to resolve the problem). I uninstalled the failing pyNN (pip uninstall). I got the code from the repository (git clone); I used the python setup.py install. PyNN runs, but I still get the same error. I don't normally install pynn from git, so I may be doing something wrong. (I also don't use a mac very often, so I may be doing something wrong there.) -Chris From: Andrew Davison ***@***.***> Sent: 27 February 2023 10:07 To: NeuralEnsemble/PyNN ***@***.***> Cc: Chris Huyck ***@***.***>; Author ***@***.***> Subject: Re: [NeuralEnsemble/PyNN] Macintosh conflict with numpy (Issue #776) Hi Chris, I believe this problem has been fixed in the master branch. We're planning to make a release sometime in the next two weeks. If you can't wait that long, please try to install PyNN from the master branch. - Reply to this email directly, view it on GitHub<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.heygears.com%2FNeuralEnsemble%2FPyNN%2Fissues%2F776%23issuecomment-1446043590&data=05%7C01%7Cc.huyck%40mdx.ac.uk%7Ce0cf5ab9c0e94e04a8ed08db18aa5278%7C38e37b88a3a148cf9f056537427fed24%7C0%7C0%7C638130892030726854%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Ink4CXjMzV%2Bk9iwj%2BE35WmhYEzENYJb0BRVPORv4A3c%3D&reserved=0>, or unsubscribe<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.heygears.com%2Fnotifications%2Funsubscribe-auth%2FAAEGLMVZFC4QFK3S5MWLRSLWZR4DBANCNFSM6AAAAAAVC77JQU&data=05%7C01%7Cc.huyck%40mdx.ac.uk%7Ce0cf5ab9c0e94e04a8ed08db18aa5278%7C38e37b88a3a148cf9f056537427fed24%7C0%7C0%7C638130892030883054%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=IajE1Cwit%2FYxxtEawx%2F7jvD5aniWyJUyY3NP3YdjaXA%3D&reserved=0>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[ChrisHuyck]

In an unrelated question, is there code for gap junction somewhere? I recall that there was some repository of models that ran in pyNN and nest, but I couldn't find it. -Chris From: Andrew Davison ***@***.***> Sent: 27 February 2023 10:07 To: NeuralEnsemble/PyNN ***@***.***> Cc: Chris Huyck ***@***.***>; Author ***@***.***> Subject: Re: [NeuralEnsemble/PyNN] Macintosh conflict with numpy (Issue #776) Hi Chris, I believe this problem has been fixed in the master branch. We're planning to make a release sometime in the next two weeks. If you can't wait that long, please try to install PyNN from the master branch. - Reply to this email directly, view it on GitHub<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.heygears.com%2FNeuralEnsemble%2FPyNN%2Fissues%2F776%23issuecomment-1446043590&data=05%7C01%7Cc.huyck%40mdx.ac.uk%7Ce0cf5ab9c0e94e04a8ed08db18aa5278%7C38e37b88a3a148cf9f056537427fed24%7C0%7C0%7C638130892030726854%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Ink4CXjMzV%2Bk9iwj%2BE35WmhYEzENYJb0BRVPORv4A3c%3D&reserved=0>, or unsubscribe<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.heygears.com%2Fnotifications%2Funsubscribe-auth%2FAAEGLMVZFC4QFK3S5MWLRSLWZR4DBANCNFSM6AAAAAAVC77JQU&data=05%7C01%7Cc.huyck%40mdx.ac.uk%7Ce0cf5ab9c0e94e04a8ed08db18aa5278%7C38e37b88a3a148cf9f056537427fed24%7C0%7C0%7C638130892030883054%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=IajE1Cwit%2FYxxtEawx%2F7jvD5aniWyJUyY3NP3YdjaXA%3D&reserved=0>. You are receiving this because you authored the thread.Message ID: ***@***.***>