Thanks for maintaining BindsNET! This is a release request, not a bug report — the underlying torch._six error is already known and correctly answered elsewhere (#619, #639) with "install from git." I'd just like to make the case for cutting a fresh PyPI release, because the current gap trips up a lot of new users.
The situation (verified):
pip install bindsnet installs 0.2.7, uploaded 2020-02-25 — 5+ years old.- 0.2.7 fails to import on any modern PyTorch:
bindsnet/datasets/collate.py and bindsnet/pipeline/base_pipeline.py import torch._six, which was removed in PyTorch 1.10.
master already fixes this — both files use collections.abc now — and the core works fine on current PyTorch. I confirmed a full Network.run simulation on torch 2.x from a git+https://... install.
So the fix has existed on master for years; it's simply never been published to PyPI. Every pip install bindsnet hands a new user a package that won't import, and they have to discover the git+ workaround (as in #619 / #639).
Ask: would you consider cutting a new PyPI release — or, if a release isn't imminent, yanking 0.2.7 with a note pointing to the git+ install? Either would save a steady stream of "ModuleNotFoundError: torch._six" reports.
Happy to help if a release checklist or a CI publish step would make it easier. Thanks again for the library!
Thanks for maintaining BindsNET! This is a release request, not a bug report — the underlying
torch._sixerror is already known and correctly answered elsewhere (#619, #639) with "install from git." I'd just like to make the case for cutting a fresh PyPI release, because the current gap trips up a lot of new users.The situation (verified):
pip install bindsnetinstalls 0.2.7, uploaded 2020-02-25 — 5+ years old.bindsnet/datasets/collate.pyandbindsnet/pipeline/base_pipeline.pyimporttorch._six, which was removed in PyTorch 1.10.masteralready fixes this — both files usecollections.abcnow — and the core works fine on current PyTorch. I confirmed a fullNetwork.runsimulation on torch 2.x from agit+https://...install.So the fix has existed on
masterfor years; it's simply never been published to PyPI. Everypip install bindsnethands a new user a package that won't import, and they have to discover thegit+workaround (as in #619 / #639).Ask: would you consider cutting a new PyPI release — or, if a release isn't imminent, yanking 0.2.7 with a note pointing to the
git+install? Either would save a steady stream of "ModuleNotFoundError: torch._six" reports.Happy to help if a release checklist or a CI publish step would make it easier. Thanks again for the library!