[Debian-med-packaging] Bug#1049671: bmtk: Fails to build binary packages again after successful build

[Lucas Nussbaum]

Source: bmtk
Version: 1.0.6+ds-1
Severity: minor
Tags: trixie sid ftbfs
User: lucas at debian.org
Usertags: ftbfs-binary-20230816 ftbfs-binary-after-build
User: debian-qa at lists.debian.org
Usertags: qa-doublebuild

Hi,

This package fails to do build a binary-only build (not source) after a
successful build (dpkg-buildpackage ; dpkg-buildpackage -b).

This is probably a clear violation of Debian Policy section 4.9 (clean target),
but this is filed as severity:minor for now, because a discussion on
debian-devel showed that we might want to revisit the requirement of a working
'clean' target.

More information about this class of issues, included common problems and
solutions, is available at
https://wiki.debian.org/qa.debian.org/FTBFS/DoubleBuild

Relevant part of the build log:
> cd /<<PKGBUILDDIR>> && runuser -u user42 -- dpkg-buildpackage --sanitize-env -us -uc -rfakeroot -b
> ------------------------------------------------------------------------------------------------------------------
> 
> dpkg-buildpackage: info: source package bmtk
> dpkg-buildpackage: info: source version 1.0.6+ds-1
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Andreas Tille <tille at debian.org>
>  dpkg-source --before-build .
> dpkg-buildpackage: info: host architecture amd64
>  debian/rules clean
> dh clean --with python3,sphinxdoc --buildsystem=pybuild
>    dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:291: python3.11 setup.py clean 
> running clean
> removing '/<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build' (and everything under it)
> 'build/bdist.linux-x86_64' does not exist -- can't clean it
> 'build/scripts-3.11' does not exist -- can't clean it
>    dh_autoreconf_clean -O--buildsystem=pybuild
>    dh_clean -O--buildsystem=pybuild
>  debian/rules binary
> dh binary --with python3,sphinxdoc --buildsystem=pybuild
>    dh_update_autotools_config -O--buildsystem=pybuild
>    dh_autoreconf -O--buildsystem=pybuild
>    dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:291: python3.11 setup.py config 
> running config
>    debian/rules override_dh_auto_build
> make[1]: Entering directory '/<<PKGBUILDDIR>>'
> dh_auto_build
> I: pybuild base:291: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk
> copying bmtk/__init__.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk
> creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator
> copying bmtk/simulator/__init__.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator
> creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/builder
> copying bmtk/builder/networks.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/builder
> copying bmtk/builder/node_pool.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/builder
> copying bmtk/builder/__init__.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/builder
> copying bmtk/builder/network_builder.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/builder
> copying bmtk/builder/node.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/builder
> copying bmtk/builder/iterator.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/builder
> copying bmtk/builder/index_builders.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/builder
> copying bmtk/builder/id_generator.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/builder
> copying bmtk/builder/connector.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/builder
> copying bmtk/builder/connection_map.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/builder
> copying bmtk/builder/edge.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/builder
> copying bmtk/builder/builder_utils.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/builder
> copying bmtk/builder/node_set.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/builder
> copying bmtk/builder/functor_cache.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/builder
> creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/analyzer
> copying bmtk/analyzer/cell_vars.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/analyzer
> copying bmtk/analyzer/utils.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/analyzer
> copying bmtk/analyzer/io_tools.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/analyzer
> copying bmtk/analyzer/__init__.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/analyzer
> copying bmtk/analyzer/ecp.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/analyzer
> copying bmtk/analyzer/firing_rates.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/analyzer
> copying bmtk/analyzer/compartment.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/analyzer
> copying bmtk/analyzer/spike_trains.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/analyzer
> copying bmtk/analyzer/spikes_loader.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/analyzer
> copying bmtk/analyzer/spikes_analyzer.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/analyzer
> creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils
> copying bmtk/utils/hdf5_helper.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils
> copying bmtk/utils/__init__.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils
> copying bmtk/utils/sim_setup.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils
> creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/bionet
> copying bmtk/simulator/bionet/bionetwork.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/bionet
> copying bmtk/simulator/bionet/utils.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/bionet
> copying bmtk/simulator/bionet/pyfunction_cache.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/bionet
> copying bmtk/simulator/bionet/io_tools.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/bionet
> copying bmtk/simulator/bionet/pointprocesscell.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/bionet
> copying bmtk/simulator/bionet/__init__.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/bionet
> copying bmtk/simulator/bionet/nml_reader.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/bionet
> copying bmtk/simulator/bionet/seclamp.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/bionet
> copying bmtk/simulator/bionet/virtualcell.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/bionet
> copying bmtk/simulator/bionet/sonata_adaptors.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/bionet
> copying bmtk/simulator/bionet/gids.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/bionet
> copying bmtk/simulator/bionet/config.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/bionet
> copying bmtk/simulator/bionet/cell.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/bionet
> copying bmtk/simulator/bionet/pointsomacell.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/bionet
> copying bmtk/simulator/bionet/morphology.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/bionet
> copying bmtk/simulator/bionet/nrn.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/bionet
> copying bmtk/simulator/bionet/biocell.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/bionet
> copying bmtk/simulator/bionet/biosimulator.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/bionet
> copying bmtk/simulator/bionet/iclamp.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/bionet
> creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/filternet
> copying bmtk/simulator/filternet/filternetwork.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/filternet
> copying bmtk/simulator/filternet/utils.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/filternet
> copying bmtk/simulator/filternet/pyfunction_cache.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/filternet
> copying bmtk/simulator/filternet/filters.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/filternet
> copying bmtk/simulator/filternet/io_tools.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/filternet
> copying bmtk/simulator/filternet/filtersimulator.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/filternet
> copying bmtk/simulator/filternet/__init__.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/filternet
> copying bmtk/simulator/filternet/sonata_adaptors.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/filternet
> copying bmtk/simulator/filternet/transfer_functions.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/filternet
> copying bmtk/simulator/filternet/config.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/filternet
> copying bmtk/simulator/filternet/cell.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/filternet
> copying bmtk/simulator/filternet/cell_models.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/filternet
> creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/pointnet
> copying bmtk/simulator/pointnet/nest_utils.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/pointnet
> copying bmtk/simulator/pointnet/utils.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/pointnet
> copying bmtk/simulator/pointnet/pyfunction_cache.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/pointnet
> copying bmtk/simulator/pointnet/io_tools.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/pointnet
> copying bmtk/simulator/pointnet/glif_utils.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/pointnet
> copying bmtk/simulator/pointnet/pointnetwork.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/pointnet
> copying bmtk/simulator/pointnet/__init__.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/pointnet
> copying bmtk/simulator/pointnet/sonata_adaptors.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/pointnet
> copying bmtk/simulator/pointnet/gids.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/pointnet
> copying bmtk/simulator/pointnet/config.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/pointnet
> copying bmtk/simulator/pointnet/property_map.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/pointnet
> copying bmtk/simulator/pointnet/pointsimulator.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/pointnet
> creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/popnet
> copying bmtk/simulator/popnet/utils.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/popnet
> copying bmtk/simulator/popnet/popsimulator.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/popnet
> copying bmtk/simulator/popnet/popedge.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/popnet
> copying bmtk/simulator/popnet/__init__.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/popnet
> copying bmtk/simulator/popnet/sonata_adaptors.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/popnet
> copying bmtk/simulator/popnet/popnode.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/popnet
> copying bmtk/simulator/popnet/config.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/popnet
> copying bmtk/simulator/popnet/popnetwork.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/popnet
> creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/utils
> copying bmtk/simulator/utils/__init__.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/utils
> copying bmtk/simulator/utils/simulation_inputs.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/utils
> copying bmtk/simulator/utils/simulation_reports.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/utils
> creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/bionet/default_setters
> copying bmtk/simulator/bionet/default_setters/__init__.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/bionet/default_setters
> copying bmtk/simulator/bionet/default_setters/synapse_models.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/bionet/default_setters
> copying bmtk/simulator/bionet/default_setters/synaptic_weights.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/bionet/default_setters
> copying bmtk/simulator/bionet/default_setters/cell_models.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/bionet/default_setters
> creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/bionet/modules
> copying bmtk/simulator/bionet/modules/xstim_waveforms.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/bionet/modules
> copying bmtk/simulator/bionet/modules/record_netcons.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/bionet/modules
> copying bmtk/simulator/bionet/modules/__init__.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/bionet/modules
> copying bmtk/simulator/bionet/modules/ecp.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/bionet/modules
> copying bmtk/simulator/bionet/modules/record_cellvars.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/bionet/modules
> copying bmtk/simulator/bionet/modules/save_synapses.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/bionet/modules
> copying bmtk/simulator/bionet/modules/xstim.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/bionet/modules
> copying bmtk/simulator/bionet/modules/record_spikes.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/bionet/modules
> copying bmtk/simulator/bionet/modules/sim_module.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/bionet/modules
> copying bmtk/simulator/bionet/modules/record_clamp.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/bionet/modules
> creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/filternet/default_setters
> copying bmtk/simulator/filternet/default_setters/__init__.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/filternet/default_setters
> copying bmtk/simulator/filternet/default_setters/cell_loaders.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/filternet/default_setters
> creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/filternet/modules
> copying bmtk/simulator/filternet/modules/base.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/filternet/modules
> copying bmtk/simulator/filternet/modules/__init__.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/filternet/modules
> copying bmtk/simulator/filternet/modules/record_rates.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/filternet/modules
> copying bmtk/simulator/filternet/modules/create_spikes.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/filternet/modules
> creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/filternet/lgnmodel
> copying bmtk/simulator/filternet/lgnmodel/spatialfilter.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/filternet/lgnmodel
> copying bmtk/simulator/filternet/lgnmodel/cursor.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/filternet/lgnmodel
> copying bmtk/simulator/filternet/lgnmodel/poissongeneration.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/filternet/lgnmodel
> copying bmtk/simulator/filternet/lgnmodel/lnunit.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/filternet/lgnmodel
> copying bmtk/simulator/filternet/lgnmodel/transferfunction.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/filternet/lgnmodel
> copying bmtk/simulator/filternet/lgnmodel/util_fns.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/filternet/lgnmodel
> copying bmtk/simulator/filternet/lgnmodel/kernel.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/filternet/lgnmodel
> copying bmtk/simulator/filternet/lgnmodel/temporalfilter.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/filternet/lgnmodel
> copying bmtk/simulator/filternet/lgnmodel/lattice_unit_constructor.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/filternet/lgnmodel
> copying bmtk/simulator/filternet/lgnmodel/movie.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/filternet/lgnmodel
> copying bmtk/simulator/filternet/lgnmodel/__init__.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/filternet/lgnmodel
> copying bmtk/simulator/filternet/lgnmodel/singleunitcell.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/filternet/lgnmodel
> copying bmtk/simulator/filternet/lgnmodel/lgnmodel1.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/filternet/lgnmodel
> copying bmtk/simulator/filternet/lgnmodel/cellmetrics.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/filternet/lgnmodel
> copying bmtk/simulator/filternet/lgnmodel/linearfilter.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/filternet/lgnmodel
> copying bmtk/simulator/filternet/lgnmodel/make_cell_list.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/filternet/lgnmodel
> copying bmtk/simulator/filternet/lgnmodel/utilities.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/filternet/lgnmodel
> copying bmtk/simulator/filternet/lgnmodel/fitfuns.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/filternet/lgnmodel
> copying bmtk/simulator/filternet/lgnmodel/cellmodel.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/filternet/lgnmodel
> creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/pointnet/default_setters
> copying bmtk/simulator/pointnet/default_setters/__init__.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/pointnet/default_setters
> copying bmtk/simulator/pointnet/default_setters/synapse_models.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/pointnet/default_setters
> copying bmtk/simulator/pointnet/default_setters/synaptic_weights.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/pointnet/default_setters
> creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/pointnet/modules
> copying bmtk/simulator/pointnet/modules/__init__.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/pointnet/modules
> copying bmtk/simulator/pointnet/modules/record_spikes.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/pointnet/modules
> copying bmtk/simulator/pointnet/modules/multimeter_reporter.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/pointnet/modules
> creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/builder/bionet
> copying bmtk/builder/bionet/swc_reader.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/builder/bionet
> copying bmtk/builder/bionet/__init__.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/builder/bionet
> creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/builder/auxi
> copying bmtk/builder/auxi/node_params.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/builder/auxi
> copying bmtk/builder/auxi/__init__.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/builder/auxi
> copying bmtk/builder/auxi/edge_connectors.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/builder/auxi
> creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/builder/network_adaptors
> copying bmtk/builder/network_adaptors/dm_network_orig.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/builder/network_adaptors
> copying bmtk/builder/network_adaptors/__init__.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/builder/network_adaptors
> copying bmtk/builder/network_adaptors/edges_collator.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/builder/network_adaptors
> copying bmtk/builder/network_adaptors/nxnetwork.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/builder/network_adaptors
> copying bmtk/builder/network_adaptors/network.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/builder/network_adaptors
> copying bmtk/builder/network_adaptors/dm_network.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/builder/network_adaptors
> copying bmtk/builder/network_adaptors/edge_props_table.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/builder/network_adaptors
> creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/builder/edges_sorter
> copying bmtk/builder/edges_sorter/__init__.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/builder/edges_sorter
> copying bmtk/builder/edges_sorter/memory_sorter.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/builder/edges_sorter
> copying bmtk/builder/edges_sorter/merge_sorter.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/builder/edges_sorter
> creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/sonata
> copying bmtk/utils/sonata/utils.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/sonata
> copying bmtk/utils/sonata/types_table.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/sonata
> copying bmtk/utils/sonata/file.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/sonata
> copying bmtk/utils/sonata/__init__.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/sonata
> copying bmtk/utils/sonata/file_root.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/sonata
> copying bmtk/utils/sonata/node.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/sonata
> copying bmtk/utils/sonata/column_property.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/sonata
> copying bmtk/utils/sonata/group.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/sonata
> copying bmtk/utils/sonata/edge.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/sonata
> copying bmtk/utils/sonata/population.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/sonata
> creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/compile_mechanisms
> copying bmtk/utils/compile_mechanisms/__main__.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/compile_mechanisms
> copying bmtk/utils/compile_mechanisms/__init__.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/compile_mechanisms
> copying bmtk/utils/compile_mechanisms/compile_mechanisms.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/compile_mechanisms
> creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/create_environment
> copying bmtk/utils/create_environment/__main__.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/create_environment
> copying bmtk/utils/create_environment/env_builder.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/create_environment
> copying bmtk/utils/create_environment/__init__.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/create_environment
> copying bmtk/utils/create_environment/create_environment.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/create_environment
> creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/io
> copying bmtk/utils/io/cell_vars.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/io
> copying bmtk/utils/io/ioutils.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/io
> copying bmtk/utils/io/__init__.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/io
> copying bmtk/utils/io/firing_rates.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/io
> copying bmtk/utils/io/spike_trains.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/io
> creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/reports
> copying bmtk/utils/reports/__init__.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/reports
> copying bmtk/utils/reports/current_writer.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/reports
> creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/sonata/config
> copying bmtk/utils/sonata/config/sonata_config.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/sonata/config
> copying bmtk/utils/sonata/config/__init__.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/sonata/config
> creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/reports/compartment
> copying bmtk/utils/reports/compartment/compartment_reader.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/reports/compartment
> copying bmtk/utils/reports/compartment/compartment_writer.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/reports/compartment
> copying bmtk/utils/reports/compartment/compartment_report.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/reports/compartment
> copying bmtk/utils/reports/compartment/core.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/reports/compartment
> copying bmtk/utils/reports/compartment/__init__.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/reports/compartment
> copying bmtk/utils/reports/compartment/plotting.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/reports/compartment
> creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/reports/spike_trains
> copying bmtk/utils/reports/spike_trains/core.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/reports/spike_trains
> copying bmtk/utils/reports/spike_trains/__init__.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/reports/spike_trains
> copying bmtk/utils/reports/spike_trains/plotting.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/reports/spike_trains
> copying bmtk/utils/reports/spike_trains/spike_train_buffer.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/reports/spike_trains
> copying bmtk/utils/reports/spike_trains/spike_trains_api.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/reports/spike_trains
> copying bmtk/utils/reports/spike_trains/spike_trains.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/reports/spike_trains
> copying bmtk/utils/reports/spike_trains/spike_train_readers.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/reports/spike_trains
> copying bmtk/utils/reports/spike_trains/spikes_file_writers.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/reports/spike_trains
> copying bmtk/utils/reports/spike_trains/stats.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/reports/spike_trains
> running egg_info
> writing bmtk.egg-info/PKG-INFO
> writing dependency_links to bmtk.egg-info/dependency_links.txt
> writing requirements to bmtk.egg-info/requires.txt
> writing top-level names to bmtk.egg-info/top_level.txt
> reading manifest file 'bmtk.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> warning: no files found matching '*.txt' under directory 'bmtk'
> warning: no files found matching '*.cfg' under directory 'bmtk'
> adding license file 'LICENSE.txt'
> writing manifest file 'bmtk.egg-info/SOURCES.txt'
> /usr/lib/python3/dist-packages/setuptools/command/build_py.py:201: _Warning: Package 'bmtk.simulator.bionet.default_templates' is absent from the `packages` configuration.
> !!
> 
>         ********************************************************************************
>         ############################
>         # Package would be ignored #
>         ############################
>         Python recognizes 'bmtk.simulator.bionet.default_templates' as an importable package[^1],
>         but it is absent from setuptools' `packages` configuration.
> 
>         This leads to an ambiguous overall configuration. If you want to distribute this
>         package, please make sure that 'bmtk.simulator.bionet.default_templates' is explicitly added
>         to the `packages` configuration field.
> 
>         Alternatively, you can also rely on setuptools' discovery methods
>         (for example by using `find_namespace_packages(...)`/`find_namespace:`
>         instead of `find_packages(...)`/`find:`).
> 
>         You can read more about "package discovery" on setuptools documentation page:
> 
>         - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
> 
>         If you don't want 'bmtk.simulator.bionet.default_templates' to be distributed and are
>         already explicitly excluding 'bmtk.simulator.bionet.default_templates' via
>         `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
>         you can try to use `exclude_package_data`, or `include-package-data=False` in
>         combination with a more fine grained `package-data` configuration.
> 
>         You can read more about "package data files" on setuptools documentation page:
> 
>         - https://setuptools.pypa.io/en/latest/userguide/datafiles.html
> 
> 
>         [^1]: For Python, any directory (with suitable naming) can be imported,
>               even if it does not contain any `.py` files.
>               On the other hand, currently there is no concept of package data
>               directory, all directories are treated like packages.
>         ********************************************************************************
> 
> !!
>   check.warn(importable)
> /usr/lib/python3/dist-packages/setuptools/command/build_py.py:201: _Warning: Package 'bmtk.simulator.bionet.import3d' is absent from the `packages` configuration.
> !!
> 
>         ********************************************************************************
>         ############################
>         # Package would be ignored #
>         ############################
>         Python recognizes 'bmtk.simulator.bionet.import3d' as an importable package[^1],
>         but it is absent from setuptools' `packages` configuration.
> 
>         This leads to an ambiguous overall configuration. If you want to distribute this
>         package, please make sure that 'bmtk.simulator.bionet.import3d' is explicitly added
>         to the `packages` configuration field.
> 
>         Alternatively, you can also rely on setuptools' discovery methods
>         (for example by using `find_namespace_packages(...)`/`find_namespace:`
>         instead of `find_packages(...)`/`find:`).
> 
>         You can read more about "package discovery" on setuptools documentation page:
> 
>         - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
> 
>         If you don't want 'bmtk.simulator.bionet.import3d' to be distributed and are
>         already explicitly excluding 'bmtk.simulator.bionet.import3d' via
>         `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
>         you can try to use `exclude_package_data`, or `include-package-data=False` in
>         combination with a more fine grained `package-data` configuration.
> 
>         You can read more about "package data files" on setuptools documentation page:
> 
>         - https://setuptools.pypa.io/en/latest/userguide/datafiles.html
> 
> 
>         [^1]: For Python, any directory (with suitable naming) can be imported,
>               even if it does not contain any `.py` files.
>               On the other hand, currently there is no concept of package data
>               directory, all directories are treated like packages.
>         ********************************************************************************
> 
> !!
>   check.warn(importable)
> /usr/lib/python3/dist-packages/setuptools/command/build_py.py:201: _Warning: Package 'bmtk.simulator.bionet.schemas' is absent from the `packages` configuration.
> !!
> 
>         ********************************************************************************
>         ############################
>         # Package would be ignored #
>         ############################
>         Python recognizes 'bmtk.simulator.bionet.schemas' as an importable package[^1],
>         but it is absent from setuptools' `packages` configuration.
> 
>         This leads to an ambiguous overall configuration. If you want to distribute this
>         package, please make sure that 'bmtk.simulator.bionet.schemas' is explicitly added
>         to the `packages` configuration field.
> 
>         Alternatively, you can also rely on setuptools' discovery methods
>         (for example by using `find_namespace_packages(...)`/`find_namespace:`
>         instead of `find_packages(...)`/`find:`).
> 
>         You can read more about "package discovery" on setuptools documentation page:
> 
>         - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
> 
>         If you don't want 'bmtk.simulator.bionet.schemas' to be distributed and are
>         already explicitly excluding 'bmtk.simulator.bionet.schemas' via
>         `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
>         you can try to use `exclude_package_data`, or `include-package-data=False` in
>         combination with a more fine grained `package-data` configuration.
> 
>         You can read more about "package data files" on setuptools documentation page:
> 
>         - https://setuptools.pypa.io/en/latest/userguide/datafiles.html
> 
> 
>         [^1]: For Python, any directory (with suitable naming) can be imported,
>               even if it does not contain any `.py` files.
>               On the other hand, currently there is no concept of package data
>               directory, all directories are treated like packages.
>         ********************************************************************************
> 
> !!
>   check.warn(importable)
> /usr/lib/python3/dist-packages/setuptools/command/build_py.py:201: _Warning: Package 'bmtk.simulator.core' is absent from the `packages` configuration.
> !!
> 
>         ********************************************************************************
>         ############################
>         # Package would be ignored #
>         ############################
>         Python recognizes 'bmtk.simulator.core' as an importable package[^1],
>         but it is absent from setuptools' `packages` configuration.
> 
>         This leads to an ambiguous overall configuration. If you want to distribute this
>         package, please make sure that 'bmtk.simulator.core' is explicitly added
>         to the `packages` configuration field.
> 
>         Alternatively, you can also rely on setuptools' discovery methods
>         (for example by using `find_namespace_packages(...)`/`find_namespace:`
>         instead of `find_packages(...)`/`find:`).
> 
>         You can read more about "package discovery" on setuptools documentation page:
> 
>         - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
> 
>         If you don't want 'bmtk.simulator.core' to be distributed and are
>         already explicitly excluding 'bmtk.simulator.core' via
>         `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
>         you can try to use `exclude_package_data`, or `include-package-data=False` in
>         combination with a more fine grained `package-data` configuration.
> 
>         You can read more about "package data files" on setuptools documentation page:
> 
>         - https://setuptools.pypa.io/en/latest/userguide/datafiles.html
> 
> 
>         [^1]: For Python, any directory (with suitable naming) can be imported,
>               even if it does not contain any `.py` files.
>               On the other hand, currently there is no concept of package data
>               directory, all directories are treated like packages.
>         ********************************************************************************
> 
> !!
>   check.warn(importable)
> /usr/lib/python3/dist-packages/setuptools/command/build_py.py:201: _Warning: Package 'bmtk.simulator.core.sonata_reader' is absent from the `packages` configuration.
> !!
> 
>         ********************************************************************************
>         ############################
>         # Package would be ignored #
>         ############################
>         Python recognizes 'bmtk.simulator.core.sonata_reader' as an importable package[^1],
>         but it is absent from setuptools' `packages` configuration.
> 
>         This leads to an ambiguous overall configuration. If you want to distribute this
>         package, please make sure that 'bmtk.simulator.core.sonata_reader' is explicitly added
>         to the `packages` configuration field.
> 
>         Alternatively, you can also rely on setuptools' discovery methods
>         (for example by using `find_namespace_packages(...)`/`find_namespace:`
>         instead of `find_packages(...)`/`find:`).
> 
>         You can read more about "package discovery" on setuptools documentation page:
> 
>         - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
> 
>         If you don't want 'bmtk.simulator.core.sonata_reader' to be distributed and are
>         already explicitly excluding 'bmtk.simulator.core.sonata_reader' via
>         `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
>         you can try to use `exclude_package_data`, or `include-package-data=False` in
>         combination with a more fine grained `package-data` configuration.
> 
>         You can read more about "package data files" on setuptools documentation page:
> 
>         - https://setuptools.pypa.io/en/latest/userguide/datafiles.html
> 
> 
>         [^1]: For Python, any directory (with suitable naming) can be imported,
>               even if it does not contain any `.py` files.
>               On the other hand, currently there is no concept of package data
>               directory, all directories are treated like packages.
>         ********************************************************************************
> 
> !!
>   check.warn(importable)
> /usr/lib/python3/dist-packages/setuptools/command/build_py.py:201: _Warning: Package 'bmtk.simulator.core.sonata_schemas' is absent from the `packages` configuration.
> !!
> 
>         ********************************************************************************
>         ############################
>         # Package would be ignored #
>         ############################
>         Python recognizes 'bmtk.simulator.core.sonata_schemas' as an importable package[^1],
>         but it is absent from setuptools' `packages` configuration.
> 
>         This leads to an ambiguous overall configuration. If you want to distribute this
>         package, please make sure that 'bmtk.simulator.core.sonata_schemas' is explicitly added
>         to the `packages` configuration field.
> 
>         Alternatively, you can also rely on setuptools' discovery methods
>         (for example by using `find_namespace_packages(...)`/`find_namespace:`
>         instead of `find_packages(...)`/`find:`).
> 
>         You can read more about "package discovery" on setuptools documentation page:
> 
>         - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
> 
>         If you don't want 'bmtk.simulator.core.sonata_schemas' to be distributed and are
>         already explicitly excluding 'bmtk.simulator.core.sonata_schemas' via
>         `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
>         you can try to use `exclude_package_data`, or `include-package-data=False` in
>         combination with a more fine grained `package-data` configuration.
> 
>         You can read more about "package data files" on setuptools documentation page:
> 
>         - https://setuptools.pypa.io/en/latest/userguide/datafiles.html
> 
> 
>         [^1]: For Python, any directory (with suitable naming) can be imported,
>               even if it does not contain any `.py` files.
>               On the other hand, currently there is no concept of package data
>               directory, all directories are treated like packages.
>         ********************************************************************************
> 
> !!
>   check.warn(importable)
> /usr/lib/python3/dist-packages/setuptools/command/build_py.py:201: _Warning: Package 'bmtk.simulator.filternet.lgnmodel.cell_metrics' is absent from the `packages` configuration.
> !!
> 
>         ********************************************************************************
>         ############################
>         # Package would be ignored #
>         ############################
>         Python recognizes 'bmtk.simulator.filternet.lgnmodel.cell_metrics' as an importable package[^1],
>         but it is absent from setuptools' `packages` configuration.
> 
>         This leads to an ambiguous overall configuration. If you want to distribute this
>         package, please make sure that 'bmtk.simulator.filternet.lgnmodel.cell_metrics' is explicitly added
>         to the `packages` configuration field.
> 
>         Alternatively, you can also rely on setuptools' discovery methods
>         (for example by using `find_namespace_packages(...)`/`find_namespace:`
>         instead of `find_packages(...)`/`find:`).
> 
>         You can read more about "package discovery" on setuptools documentation page:
> 
>         - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
> 
>         If you don't want 'bmtk.simulator.filternet.lgnmodel.cell_metrics' to be distributed and are
>         already explicitly excluding 'bmtk.simulator.filternet.lgnmodel.cell_metrics' via
>         `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
>         you can try to use `exclude_package_data`, or `include-package-data=False` in
>         combination with a more fine grained `package-data` configuration.
> 
>         You can read more about "package data files" on setuptools documentation page:
> 
>         - https://setuptools.pypa.io/en/latest/userguide/datafiles.html
> 
> 
>         [^1]: For Python, any directory (with suitable naming) can be imported,
>               even if it does not contain any `.py` files.
>               On the other hand, currently there is no concept of package data
>               directory, all directories are treated like packages.
>         ********************************************************************************
> 
> !!
>   check.warn(importable)
> /usr/lib/python3/dist-packages/setuptools/command/build_py.py:201: _Warning: Package 'bmtk.utils.scripts' is absent from the `packages` configuration.
> !!
> 
>         ********************************************************************************
>         ############################
>         # Package would be ignored #
>         ############################
>         Python recognizes 'bmtk.utils.scripts' as an importable package[^1],
>         but it is absent from setuptools' `packages` configuration.
> 
>         This leads to an ambiguous overall configuration. If you want to distribute this
>         package, please make sure that 'bmtk.utils.scripts' is explicitly added
>         to the `packages` configuration field.
> 
>         Alternatively, you can also rely on setuptools' discovery methods
>         (for example by using `find_namespace_packages(...)`/`find_namespace:`
>         instead of `find_packages(...)`/`find:`).
> 
>         You can read more about "package discovery" on setuptools documentation page:
> 
>         - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
> 
>         If you don't want 'bmtk.utils.scripts' to be distributed and are
>         already explicitly excluding 'bmtk.utils.scripts' via
>         `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
>         you can try to use `exclude_package_data`, or `include-package-data=False` in
>         combination with a more fine grained `package-data` configuration.
> 
>         You can read more about "package data files" on setuptools documentation page:
> 
>         - https://setuptools.pypa.io/en/latest/userguide/datafiles.html
> 
> 
>         [^1]: For Python, any directory (with suitable naming) can be imported,
>               even if it does not contain any `.py` files.
>               On the other hand, currently there is no concept of package data
>               directory, all directories are treated like packages.
>         ********************************************************************************
> 
> !!
>   check.warn(importable)
> /usr/lib/python3/dist-packages/setuptools/command/build_py.py:201: _Warning: Package 'bmtk.utils.scripts.bionet' is absent from the `packages` configuration.
> !!
> 
>         ********************************************************************************
>         ############################
>         # Package would be ignored #
>         ############################
>         Python recognizes 'bmtk.utils.scripts.bionet' as an importable package[^1],
>         but it is absent from setuptools' `packages` configuration.
> 
>         This leads to an ambiguous overall configuration. If you want to distribute this
>         package, please make sure that 'bmtk.utils.scripts.bionet' is explicitly added
>         to the `packages` configuration field.
> 
>         Alternatively, you can also rely on setuptools' discovery methods
>         (for example by using `find_namespace_packages(...)`/`find_namespace:`
>         instead of `find_packages(...)`/`find:`).
> 
>         You can read more about "package discovery" on setuptools documentation page:
> 
>         - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
> 
>         If you don't want 'bmtk.utils.scripts.bionet' to be distributed and are
>         already explicitly excluding 'bmtk.utils.scripts.bionet' via
>         `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
>         you can try to use `exclude_package_data`, or `include-package-data=False` in
>         combination with a more fine grained `package-data` configuration.
> 
>         You can read more about "package data files" on setuptools documentation page:
> 
>         - https://setuptools.pypa.io/en/latest/userguide/datafiles.html
> 
> 
>         [^1]: For Python, any directory (with suitable naming) can be imported,
>               even if it does not contain any `.py` files.
>               On the other hand, currently there is no concept of package data
>               directory, all directories are treated like packages.
>         ********************************************************************************
> 
> !!
>   check.warn(importable)
> /usr/lib/python3/dist-packages/setuptools/command/build_py.py:201: _Warning: Package 'bmtk.utils.scripts.bionet.biophysical_neuron_models' is absent from the `packages` configuration.
> !!
> 
>         ********************************************************************************
>         ############################
>         # Package would be ignored #
>         ############################
>         Python recognizes 'bmtk.utils.scripts.bionet.biophysical_neuron_models' as an importable package[^1],
>         but it is absent from setuptools' `packages` configuration.
> 
>         This leads to an ambiguous overall configuration. If you want to distribute this
>         package, please make sure that 'bmtk.utils.scripts.bionet.biophysical_neuron_models' is explicitly added
>         to the `packages` configuration field.
> 
>         Alternatively, you can also rely on setuptools' discovery methods
>         (for example by using `find_namespace_packages(...)`/`find_namespace:`
>         instead of `find_packages(...)`/`find:`).
> 
>         You can read more about "package discovery" on setuptools documentation page:
> 
>         - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
> 
>         If you don't want 'bmtk.utils.scripts.bionet.biophysical_neuron_models' to be distributed and are
>         already explicitly excluding 'bmtk.utils.scripts.bionet.biophysical_neuron_models' via
>         `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
>         you can try to use `exclude_package_data`, or `include-package-data=False` in
>         combination with a more fine grained `package-data` configuration.
> 
>         You can read more about "package data files" on setuptools documentation page:
> 
>         - https://setuptools.pypa.io/en/latest/userguide/datafiles.html
> 
> 
>         [^1]: For Python, any directory (with suitable naming) can be imported,
>               even if it does not contain any `.py` files.
>               On the other hand, currently there is no concept of package data
>               directory, all directories are treated like packages.
>         ********************************************************************************
> 
> !!
>   check.warn(importable)
> /usr/lib/python3/dist-packages/setuptools/command/build_py.py:201: _Warning: Package 'bmtk.utils.scripts.bionet.filter_models' is absent from the `packages` configuration.
> !!
> 
>         ********************************************************************************
>         ############################
>         # Package would be ignored #
>         ############################
>         Python recognizes 'bmtk.utils.scripts.bionet.filter_models' as an importable package[^1],
>         but it is absent from setuptools' `packages` configuration.
> 
>         This leads to an ambiguous overall configuration. If you want to distribute this
>         package, please make sure that 'bmtk.utils.scripts.bionet.filter_models' is explicitly added
>         to the `packages` configuration field.
> 
>         Alternatively, you can also rely on setuptools' discovery methods
>         (for example by using `find_namespace_packages(...)`/`find_namespace:`
>         instead of `find_packages(...)`/`find:`).
> 
>         You can read more about "package discovery" on setuptools documentation page:
> 
>         - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
> 
>         If you don't want 'bmtk.utils.scripts.bionet.filter_models' to be distributed and are
>         already explicitly excluding 'bmtk.utils.scripts.bionet.filter_models' via
>         `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
>         you can try to use `exclude_package_data`, or `include-package-data=False` in
>         combination with a more fine grained `package-data` configuration.
> 
>         You can read more about "package data files" on setuptools documentation page:
> 
>         - https://setuptools.pypa.io/en/latest/userguide/datafiles.html
> 
> 
>         [^1]: For Python, any directory (with suitable naming) can be imported,
>               even if it does not contain any `.py` files.
>               On the other hand, currently there is no concept of package data
>               directory, all directories are treated like packages.
>         ********************************************************************************
> 
> !!
>   check.warn(importable)
> /usr/lib/python3/dist-packages/setuptools/command/build_py.py:201: _Warning: Package 'bmtk.utils.scripts.bionet.mechanisms.modfiles' is absent from the `packages` configuration.
> !!
> 
>         ********************************************************************************
>         ############################
>         # Package would be ignored #
>         ############################
>         Python recognizes 'bmtk.utils.scripts.bionet.mechanisms.modfiles' as an importable package[^1],
>         but it is absent from setuptools' `packages` configuration.
> 
>         This leads to an ambiguous overall configuration. If you want to distribute this
>         package, please make sure that 'bmtk.utils.scripts.bionet.mechanisms.modfiles' is explicitly added
>         to the `packages` configuration field.
> 
>         Alternatively, you can also rely on setuptools' discovery methods
>         (for example by using `find_namespace_packages(...)`/`find_namespace:`
>         instead of `find_packages(...)`/`find:`).
> 
>         You can read more about "package discovery" on setuptools documentation page:
> 
>         - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
> 
>         If you don't want 'bmtk.utils.scripts.bionet.mechanisms.modfiles' to be distributed and are
>         already explicitly excluding 'bmtk.utils.scripts.bionet.mechanisms.modfiles' via
>         `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
>         you can try to use `exclude_package_data`, or `include-package-data=False` in
>         combination with a more fine grained `package-data` configuration.
> 
>         You can read more about "package data files" on setuptools documentation page:
> 
>         - https://setuptools.pypa.io/en/latest/userguide/datafiles.html
> 
> 
>         [^1]: For Python, any directory (with suitable naming) can be imported,
>               even if it does not contain any `.py` files.
>               On the other hand, currently there is no concept of package data
>               directory, all directories are treated like packages.
>         ********************************************************************************
> 
> !!
>   check.warn(importable)
> /usr/lib/python3/dist-packages/setuptools/command/build_py.py:201: _Warning: Package 'bmtk.utils.scripts.bionet.morphologies' is absent from the `packages` configuration.
> !!
> 
>         ********************************************************************************
>         ############################
>         # Package would be ignored #
>         ############################
>         Python recognizes 'bmtk.utils.scripts.bionet.morphologies' as an importable package[^1],
>         but it is absent from setuptools' `packages` configuration.
> 
>         This leads to an ambiguous overall configuration. If you want to distribute this
>         package, please make sure that 'bmtk.utils.scripts.bionet.morphologies' is explicitly added
>         to the `packages` configuration field.
> 
>         Alternatively, you can also rely on setuptools' discovery methods
>         (for example by using `find_namespace_packages(...)`/`find_namespace:`
>         instead of `find_packages(...)`/`find:`).
> 
>         You can read more about "package discovery" on setuptools documentation page:
> 
>         - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
> 
>         If you don't want 'bmtk.utils.scripts.bionet.morphologies' to be distributed and are
>         already explicitly excluding 'bmtk.utils.scripts.bionet.morphologies' via
>         `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
>         you can try to use `exclude_package_data`, or `include-package-data=False` in
>         combination with a more fine grained `package-data` configuration.
> 
>         You can read more about "package data files" on setuptools documentation page:
> 
>         - https://setuptools.pypa.io/en/latest/userguide/datafiles.html
> 
> 
>         [^1]: For Python, any directory (with suitable naming) can be imported,
>               even if it does not contain any `.py` files.
>               On the other hand, currently there is no concept of package data
>               directory, all directories are treated like packages.
>         ********************************************************************************
> 
> !!
>   check.warn(importable)
> /usr/lib/python3/dist-packages/setuptools/command/build_py.py:201: _Warning: Package 'bmtk.utils.scripts.bionet.point_neuron_models' is absent from the `packages` configuration.
> !!
> 
>         ********************************************************************************
>         ############################
>         # Package would be ignored #
>         ############################
>         Python recognizes 'bmtk.utils.scripts.bionet.point_neuron_models' as an importable package[^1],
>         but it is absent from setuptools' `packages` configuration.
> 
>         This leads to an ambiguous overall configuration. If you want to distribute this
>         package, please make sure that 'bmtk.utils.scripts.bionet.point_neuron_models' is explicitly added
>         to the `packages` configuration field.
> 
>         Alternatively, you can also rely on setuptools' discovery methods
>         (for example by using `find_namespace_packages(...)`/`find_namespace:`
>         instead of `find_packages(...)`/`find:`).
> 
>         You can read more about "package discovery" on setuptools documentation page:
> 
>         - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
> 
>         If you don't want 'bmtk.utils.scripts.bionet.point_neuron_models' to be distributed and are
>         already explicitly excluding 'bmtk.utils.scripts.bionet.point_neuron_models' via
>         `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
>         you can try to use `exclude_package_data`, or `include-package-data=False` in
>         combination with a more fine grained `package-data` configuration.
> 
>         You can read more about "package data files" on setuptools documentation page:
> 
>         - https://setuptools.pypa.io/en/latest/userguide/datafiles.html
> 
> 
>         [^1]: For Python, any directory (with suitable naming) can be imported,
>               even if it does not contain any `.py` files.
>               On the other hand, currently there is no concept of package data
>               directory, all directories are treated like packages.
>         ********************************************************************************
> 
> !!
>   check.warn(importable)
> /usr/lib/python3/dist-packages/setuptools/command/build_py.py:201: _Warning: Package 'bmtk.utils.scripts.bionet.synaptic_models' is absent from the `packages` configuration.
> !!
> 
>         ********************************************************************************
>         ############################
>         # Package would be ignored #
>         ############################
>         Python recognizes 'bmtk.utils.scripts.bionet.synaptic_models' as an importable package[^1],
>         but it is absent from setuptools' `packages` configuration.
> 
>         This leads to an ambiguous overall configuration. If you want to distribute this
>         package, please make sure that 'bmtk.utils.scripts.bionet.synaptic_models' is explicitly added
>         to the `packages` configuration field.
> 
>         Alternatively, you can also rely on setuptools' discovery methods
>         (for example by using `find_namespace_packages(...)`/`find_namespace:`
>         instead of `find_packages(...)`/`find:`).
> 
>         You can read more about "package discovery" on setuptools documentation page:
> 
>         - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
> 
>         If you don't want 'bmtk.utils.scripts.bionet.synaptic_models' to be distributed and are
>         already explicitly excluding 'bmtk.utils.scripts.bionet.synaptic_models' via
>         `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
>         you can try to use `exclude_package_data`, or `include-package-data=False` in
>         combination with a more fine grained `package-data` configuration.
> 
>         You can read more about "package data files" on setuptools documentation page:
> 
>         - https://setuptools.pypa.io/en/latest/userguide/datafiles.html
> 
> 
>         [^1]: For Python, any directory (with suitable naming) can be imported,
>               even if it does not contain any `.py` files.
>               On the other hand, currently there is no concept of package data
>               directory, all directories are treated like packages.
>         ********************************************************************************
> 
> !!
>   check.warn(importable)
> /usr/lib/python3/dist-packages/setuptools/command/build_py.py:201: _Warning: Package 'bmtk.utils.scripts.bionet.templates' is absent from the `packages` configuration.
> !!
> 
>         ********************************************************************************
>         ############################
>         # Package would be ignored #
>         ############################
>         Python recognizes 'bmtk.utils.scripts.bionet.templates' as an importable package[^1],
>         but it is absent from setuptools' `packages` configuration.
> 
>         This leads to an ambiguous overall configuration. If you want to distribute this
>         package, please make sure that 'bmtk.utils.scripts.bionet.templates' is explicitly added
>         to the `packages` configuration field.
> 
>         Alternatively, you can also rely on setuptools' discovery methods
>         (for example by using `find_namespace_packages(...)`/`find_namespace:`
>         instead of `find_packages(...)`/`find:`).
> 
>         You can read more about "package discovery" on setuptools documentation page:
> 
>         - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
> 
>         If you don't want 'bmtk.utils.scripts.bionet.templates' to be distributed and are
>         already explicitly excluding 'bmtk.utils.scripts.bionet.templates' via
>         `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
>         you can try to use `exclude_package_data`, or `include-package-data=False` in
>         combination with a more fine grained `package-data` configuration.
> 
>         You can read more about "package data files" on setuptools documentation page:
> 
>         - https://setuptools.pypa.io/en/latest/userguide/datafiles.html
> 
> 
>         [^1]: For Python, any directory (with suitable naming) can be imported,
>               even if it does not contain any `.py` files.
>               On the other hand, currently there is no concept of package data
>               directory, all directories are treated like packages.
>         ********************************************************************************
> 
> !!
>   check.warn(importable)
> /usr/lib/python3/dist-packages/setuptools/command/build_py.py:201: _Warning: Package 'bmtk.utils.scripts.filternet' is absent from the `packages` configuration.
> !!
> 
>         ********************************************************************************
>         ############################
>         # Package would be ignored #
>         ############################
>         Python recognizes 'bmtk.utils.scripts.filternet' as an importable package[^1],
>         but it is absent from setuptools' `packages` configuration.
> 
>         This leads to an ambiguous overall configuration. If you want to distribute this
>         package, please make sure that 'bmtk.utils.scripts.filternet' is explicitly added
>         to the `packages` configuration field.
> 
>         Alternatively, you can also rely on setuptools' discovery methods
>         (for example by using `find_namespace_packages(...)`/`find_namespace:`
>         instead of `find_packages(...)`/`find:`).
> 
>         You can read more about "package discovery" on setuptools documentation page:
> 
>         - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
> 
>         If you don't want 'bmtk.utils.scripts.filternet' to be distributed and are
>         already explicitly excluding 'bmtk.utils.scripts.filternet' via
>         `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
>         you can try to use `exclude_package_data`, or `include-package-data=False` in
>         combination with a more fine grained `package-data` configuration.
> 
>         You can read more about "package data files" on setuptools documentation page:
> 
>         - https://setuptools.pypa.io/en/latest/userguide/datafiles.html
> 
> 
>         [^1]: For Python, any directory (with suitable naming) can be imported,
>               even if it does not contain any `.py` files.
>               On the other hand, currently there is no concept of package data
>               directory, all directories are treated like packages.
>         ********************************************************************************
> 
> !!
>   check.warn(importable)
> /usr/lib/python3/dist-packages/setuptools/command/build_py.py:201: _Warning: Package 'bmtk.utils.scripts.filternet.filter_models' is absent from the `packages` configuration.
> !!
> 
>         ********************************************************************************
>         ############################
>         # Package would be ignored #
>         ############################
>         Python recognizes 'bmtk.utils.scripts.filternet.filter_models' as an importable package[^1],
>         but it is absent from setuptools' `packages` configuration.
> 
>         This leads to an ambiguous overall configuration. If you want to distribute this
>         package, please make sure that 'bmtk.utils.scripts.filternet.filter_models' is explicitly added
>         to the `packages` configuration field.
> 
>         Alternatively, you can also rely on setuptools' discovery methods
>         (for example by using `find_namespace_packages(...)`/`find_namespace:`
>         instead of `find_packages(...)`/`find:`).
> 
>         You can read more about "package discovery" on setuptools documentation page:
> 
>         - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
> 
>         If you don't want 'bmtk.utils.scripts.filternet.filter_models' to be distributed and are
>         already explicitly excluding 'bmtk.utils.scripts.filternet.filter_models' via
>         `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
>         you can try to use `exclude_package_data`, or `include-package-data=False` in
>         combination with a more fine grained `package-data` configuration.
> 
>         You can read more about "package data files" on setuptools documentation page:
> 
>         - https://setuptools.pypa.io/en/latest/userguide/datafiles.html
> 
> 
>         [^1]: For Python, any directory (with suitable naming) can be imported,
>               even if it does not contain any `.py` files.
>               On the other hand, currently there is no concept of package data
>               directory, all directories are treated like packages.
>         ********************************************************************************
> 
> !!
>   check.warn(importable)
> /usr/lib/python3/dist-packages/setuptools/command/build_py.py:201: _Warning: Package 'bmtk.utils.scripts.pointnet' is absent from the `packages` configuration.
> !!
> 
>         ********************************************************************************
>         ############################
>         # Package would be ignored #
>         ############################
>         Python recognizes 'bmtk.utils.scripts.pointnet' as an importable package[^1],
>         but it is absent from setuptools' `packages` configuration.
> 
>         This leads to an ambiguous overall configuration. If you want to distribute this
>         package, please make sure that 'bmtk.utils.scripts.pointnet' is explicitly added
>         to the `packages` configuration field.
> 
>         Alternatively, you can also rely on setuptools' discovery methods
>         (for example by using `find_namespace_packages(...)`/`find_namespace:`
>         instead of `find_packages(...)`/`find:`).
> 
>         You can read more about "package discovery" on setuptools documentation page:
> 
>         - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
> 
>         If you don't want 'bmtk.utils.scripts.pointnet' to be distributed and are
>         already explicitly excluding 'bmtk.utils.scripts.pointnet' via
>         `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
>         you can try to use `exclude_package_data`, or `include-package-data=False` in
>         combination with a more fine grained `package-data` configuration.
> 
>         You can read more about "package data files" on setuptools documentation page:
> 
>         - https://setuptools.pypa.io/en/latest/userguide/datafiles.html
> 
> 
>         [^1]: For Python, any directory (with suitable naming) can be imported,
>               even if it does not contain any `.py` files.
>               On the other hand, currently there is no concept of package data
>               directory, all directories are treated like packages.
>         ********************************************************************************
> 
> !!
>   check.warn(importable)
> /usr/lib/python3/dist-packages/setuptools/command/build_py.py:201: _Warning: Package 'bmtk.utils.scripts.pointnet.filter_models' is absent from the `packages` configuration.
> !!
> 
>         ********************************************************************************
>         ############################
>         # Package would be ignored #
>         ############################
>         Python recognizes 'bmtk.utils.scripts.pointnet.filter_models' as an importable package[^1],
>         but it is absent from setuptools' `packages` configuration.
> 
>         This leads to an ambiguous overall configuration. If you want to distribute this
>         package, please make sure that 'bmtk.utils.scripts.pointnet.filter_models' is explicitly added
>         to the `packages` configuration field.
> 
>         Alternatively, you can also rely on setuptools' discovery methods
>         (for example by using `find_namespace_packages(...)`/`find_namespace:`
>         instead of `find_packages(...)`/`find:`).
> 
>         You can read more about "package discovery" on setuptools documentation page:
> 
>         - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
> 
>         If you don't want 'bmtk.utils.scripts.pointnet.filter_models' to be distributed and are
>         already explicitly excluding 'bmtk.utils.scripts.pointnet.filter_models' via
>         `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
>         you can try to use `exclude_package_data`, or `include-package-data=False` in
>         combination with a more fine grained `package-data` configuration.
> 
>         You can read more about "package data files" on setuptools documentation page:
> 
>         - https://setuptools.pypa.io/en/latest/userguide/datafiles.html
> 
> 
>         [^1]: For Python, any directory (with suitable naming) can be imported,
>               even if it does not contain any `.py` files.
>               On the other hand, currently there is no concept of package data
>               directory, all directories are treated like packages.
>         ********************************************************************************
> 
> !!
>   check.warn(importable)
> /usr/lib/python3/dist-packages/setuptools/command/build_py.py:201: _Warning: Package 'bmtk.utils.scripts.pointnet.point_neuron_models' is absent from the `packages` configuration.
> !!
> 
>         ********************************************************************************
>         ############################
>         # Package would be ignored #
>         ############################
>         Python recognizes 'bmtk.utils.scripts.pointnet.point_neuron_models' as an importable package[^1],
>         but it is absent from setuptools' `packages` configuration.
> 
>         This leads to an ambiguous overall configuration. If you want to distribute this
>         package, please make sure that 'bmtk.utils.scripts.pointnet.point_neuron_models' is explicitly added
>         to the `packages` configuration field.
> 
>         Alternatively, you can also rely on setuptools' discovery methods
>         (for example by using `find_namespace_packages(...)`/`find_namespace:`
>         instead of `find_packages(...)`/`find:`).
> 
>         You can read more about "package discovery" on setuptools documentation page:
> 
>         - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
> 
>         If you don't want 'bmtk.utils.scripts.pointnet.point_neuron_models' to be distributed and are
>         already explicitly excluding 'bmtk.utils.scripts.pointnet.point_neuron_models' via
>         `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
>         you can try to use `exclude_package_data`, or `include-package-data=False` in
>         combination with a more fine grained `package-data` configuration.
> 
>         You can read more about "package data files" on setuptools documentation page:
> 
>         - https://setuptools.pypa.io/en/latest/userguide/datafiles.html
> 
> 
>         [^1]: For Python, any directory (with suitable naming) can be imported,
>               even if it does not contain any `.py` files.
>               On the other hand, currently there is no concept of package data
>               directory, all directories are treated like packages.
>         ********************************************************************************
> 
> !!
>   check.warn(importable)
> /usr/lib/python3/dist-packages/setuptools/command/build_py.py:201: _Warning: Package 'bmtk.utils.scripts.pointnet.synaptic_models' is absent from the `packages` configuration.
> !!
> 
>         ********************************************************************************
>         ############################
>         # Package would be ignored #
>         ############################
>         Python recognizes 'bmtk.utils.scripts.pointnet.synaptic_models' as an importable package[^1],
>         but it is absent from setuptools' `packages` configuration.
> 
>         This leads to an ambiguous overall configuration. If you want to distribute this
>         package, please make sure that 'bmtk.utils.scripts.pointnet.synaptic_models' is explicitly added
>         to the `packages` configuration field.
> 
>         Alternatively, you can also rely on setuptools' discovery methods
>         (for example by using `find_namespace_packages(...)`/`find_namespace:`
>         instead of `find_packages(...)`/`find:`).
> 
>         You can read more about "package discovery" on setuptools documentation page:
> 
>         - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
> 
>         If you don't want 'bmtk.utils.scripts.pointnet.synaptic_models' to be distributed and are
>         already explicitly excluding 'bmtk.utils.scripts.pointnet.synaptic_models' via
>         `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
>         you can try to use `exclude_package_data`, or `include-package-data=False` in
>         combination with a more fine grained `package-data` configuration.
> 
>         You can read more about "package data files" on setuptools documentation page:
> 
>         - https://setuptools.pypa.io/en/latest/userguide/datafiles.html
> 
> 
>         [^1]: For Python, any directory (with suitable naming) can be imported,
>               even if it does not contain any `.py` files.
>               On the other hand, currently there is no concept of package data
>               directory, all directories are treated like packages.
>         ********************************************************************************
> 
> !!
>   check.warn(importable)
> /usr/lib/python3/dist-packages/setuptools/command/build_py.py:201: _Warning: Package 'bmtk.utils.scripts.popnet' is absent from the `packages` configuration.
> !!
> 
>         ********************************************************************************
>         ############################
>         # Package would be ignored #
>         ############################
>         Python recognizes 'bmtk.utils.scripts.popnet' as an importable package[^1],
>         but it is absent from setuptools' `packages` configuration.
> 
>         This leads to an ambiguous overall configuration. If you want to distribute this
>         package, please make sure that 'bmtk.utils.scripts.popnet' is explicitly added
>         to the `packages` configuration field.
> 
>         Alternatively, you can also rely on setuptools' discovery methods
>         (for example by using `find_namespace_packages(...)`/`find_namespace:`
>         instead of `find_packages(...)`/`find:`).
> 
>         You can read more about "package discovery" on setuptools documentation page:
> 
>         - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
> 
>         If you don't want 'bmtk.utils.scripts.popnet' to be distributed and are
>         already explicitly excluding 'bmtk.utils.scripts.popnet' via
>         `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
>         you can try to use `exclude_package_data`, or `include-package-data=False` in
>         combination with a more fine grained `package-data` configuration.
> 
>         You can read more about "package data files" on setuptools documentation page:
> 
>         - https://setuptools.pypa.io/en/latest/userguide/datafiles.html
> 
> 
>         [^1]: For Python, any directory (with suitable naming) can be imported,
>               even if it does not contain any `.py` files.
>               On the other hand, currently there is no concept of package data
>               directory, all directories are treated like packages.
>         ********************************************************************************
> 
> !!
>   check.warn(importable)
> /usr/lib/python3/dist-packages/setuptools/command/build_py.py:201: _Warning: Package 'bmtk.utils.scripts.popnet.population_models' is absent from the `packages` configuration.
> !!
> 
>         ********************************************************************************
>         ############################
>         # Package would be ignored #
>         ############################
>         Python recognizes 'bmtk.utils.scripts.popnet.population_models' as an importable package[^1],
>         but it is absent from setuptools' `packages` configuration.
> 
>         This leads to an ambiguous overall configuration. If you want to distribute this
>         package, please make sure that 'bmtk.utils.scripts.popnet.population_models' is explicitly added
>         to the `packages` configuration field.
> 
>         Alternatively, you can also rely on setuptools' discovery methods
>         (for example by using `find_namespace_packages(...)`/`find_namespace:`
>         instead of `find_packages(...)`/`find:`).
> 
>         You can read more about "package discovery" on setuptools documentation page:
> 
>         - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
> 
>         If you don't want 'bmtk.utils.scripts.popnet.population_models' to be distributed and are
>         already explicitly excluding 'bmtk.utils.scripts.popnet.population_models' via
>         `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
>         you can try to use `exclude_package_data`, or `include-package-data=False` in
>         combination with a more fine grained `package-data` configuration.
> 
>         You can read more about "package data files" on setuptools documentation page:
> 
>         - https://setuptools.pypa.io/en/latest/userguide/datafiles.html
> 
> 
>         [^1]: For Python, any directory (with suitable naming) can be imported,
>               even if it does not contain any `.py` files.
>               On the other hand, currently there is no concept of package data
>               directory, all directories are treated like packages.
>         ********************************************************************************
> 
> !!
>   check.warn(importable)
> /usr/lib/python3/dist-packages/setuptools/command/build_py.py:201: _Warning: Package 'bmtk.utils.scripts.popnet.synaptic_models' is absent from the `packages` configuration.
> !!
> 
>         ********************************************************************************
>         ############################
>         # Package would be ignored #
>         ############################
>         Python recognizes 'bmtk.utils.scripts.popnet.synaptic_models' as an importable package[^1],
>         but it is absent from setuptools' `packages` configuration.
> 
>         This leads to an ambiguous overall configuration. If you want to distribute this
>         package, please make sure that 'bmtk.utils.scripts.popnet.synaptic_models' is explicitly added
>         to the `packages` configuration field.
> 
>         Alternatively, you can also rely on setuptools' discovery methods
>         (for example by using `find_namespace_packages(...)`/`find_namespace:`
>         instead of `find_packages(...)`/`find:`).
> 
>         You can read more about "package discovery" on setuptools documentation page:
> 
>         - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
> 
>         If you don't want 'bmtk.utils.scripts.popnet.synaptic_models' to be distributed and are
>         already explicitly excluding 'bmtk.utils.scripts.popnet.synaptic_models' via
>         `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
>         you can try to use `exclude_package_data`, or `include-package-data=False` in
>         combination with a more fine grained `package-data` configuration.
> 
>         You can read more about "package data files" on setuptools documentation page:
> 
>         - https://setuptools.pypa.io/en/latest/userguide/datafiles.html
> 
> 
>         [^1]: For Python, any directory (with suitable naming) can be imported,
>               even if it does not contain any `.py` files.
>               On the other hand, currently there is no concept of package data
>               directory, all directories are treated like packages.
>         ********************************************************************************
> 
> !!
>   check.warn(importable)
> creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/core
> copying bmtk/simulator/core/edge_population.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/core
> copying bmtk/simulator/core/graph.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/core
> copying bmtk/simulator/core/io_tools.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/core
> copying bmtk/simulator/core/network_reader.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/core
> copying bmtk/simulator/core/node_population.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/core
> copying bmtk/simulator/core/node_sets.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/core
> copying bmtk/simulator/core/pyfunction_cache.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/core
> copying bmtk/simulator/core/simulation_config.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/core
> copying bmtk/simulator/core/simulation_config_validator.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/core
> copying bmtk/simulator/core/simulator.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/core
> copying bmtk/simulator/core/simulator_network.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/core
> creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/core/sonata_reader
> copying bmtk/simulator/core/sonata_reader/__init__.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/core/sonata_reader
> copying bmtk/simulator/core/sonata_reader/edge_adaptor.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/core/sonata_reader
> copying bmtk/simulator/core/sonata_reader/network_reader.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/core/sonata_reader
> copying bmtk/simulator/core/sonata_reader/node_adaptor.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/core/sonata_reader
> creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/core/sonata_schemas
> copying bmtk/simulator/core/sonata_schemas/config_schema.json -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/core/sonata_schemas
> creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts
> copying bmtk/utils/scripts/sonata.circuit_config.json -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts
> copying bmtk/utils/scripts/sonata.simulation_config.json -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts
> creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/bionet
> copying bmtk/utils/scripts/bionet/default_config.json -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/bionet
> copying bmtk/utils/scripts/bionet/run_bionet.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/bionet
> creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/bionet/biophysical_neuron_models
> copying bmtk/utils/scripts/bionet/biophysical_neuron_models/318331342_fit.json -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/bionet/biophysical_neuron_models
> copying bmtk/utils/scripts/bionet/biophysical_neuron_models/472363762_fit.json -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/bionet/biophysical_neuron_models
> copying bmtk/utils/scripts/bionet/biophysical_neuron_models/472912177_fit.json -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/bionet/biophysical_neuron_models
> copying bmtk/utils/scripts/bionet/biophysical_neuron_models/473862421_fit.json -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/bionet/biophysical_neuron_models
> copying bmtk/utils/scripts/bionet/biophysical_neuron_models/473863035_fit.json -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/bionet/biophysical_neuron_models
> copying bmtk/utils/scripts/bionet/biophysical_neuron_models/473863510_fit.json -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/bionet/biophysical_neuron_models
> copying bmtk/utils/scripts/bionet/biophysical_neuron_models/485184849_fit.json -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/bionet/biophysical_neuron_models
> creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/bionet/filter_models
> copying bmtk/utils/scripts/bionet/filter_models/sOFF_TF1.json -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/bionet/filter_models
> copying bmtk/utils/scripts/bionet/filter_models/sOFF_TF15.json -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/bionet/filter_models
> copying bmtk/utils/scripts/bionet/filter_models/sOFF_TF2.json -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/bionet/filter_models
> copying bmtk/utils/scripts/bionet/filter_models/sOFF_TF4.json -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/bionet/filter_models
> copying bmtk/utils/scripts/bionet/filter_models/sOFF_TF8.json -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/bionet/filter_models
> copying bmtk/utils/scripts/bionet/filter_models/sON_TF1.json -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/bionet/filter_models
> copying bmtk/utils/scripts/bionet/filter_models/sON_TF2.json -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/bionet/filter_models
> copying bmtk/utils/scripts/bionet/filter_models/sON_TF4.json -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/bionet/filter_models
> copying bmtk/utils/scripts/bionet/filter_models/sON_TF8.json -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/bionet/filter_models
> copying bmtk/utils/scripts/bionet/filter_models/tOFF_TF15.json -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/bionet/filter_models
> copying bmtk/utils/scripts/bionet/filter_models/tOFF_TF4.json -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/bionet/filter_models
> copying bmtk/utils/scripts/bionet/filter_models/tOFF_TF8.json -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/bionet/filter_models
> creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/bionet/mechanisms
> creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/bionet/mechanisms/modfiles
> copying bmtk/utils/scripts/bionet/mechanisms/modfiles/CaDynamics.mod -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/bionet/mechanisms/modfiles
> copying bmtk/utils/scripts/bionet/mechanisms/modfiles/Ca_HVA.mod -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/bionet/mechanisms/modfiles
> copying bmtk/utils/scripts/bionet/mechanisms/modfiles/Ca_LVA.mod -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/bionet/mechanisms/modfiles
> copying bmtk/utils/scripts/bionet/mechanisms/modfiles/Ih.mod -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/bionet/mechanisms/modfiles
> copying bmtk/utils/scripts/bionet/mechanisms/modfiles/Im.mod -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/bionet/mechanisms/modfiles
> copying bmtk/utils/scripts/bionet/mechanisms/modfiles/Im_v2.mod -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/bionet/mechanisms/modfiles
> copying bmtk/utils/scripts/bionet/mechanisms/modfiles/K_P.mod -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/bionet/mechanisms/modfiles
> copying bmtk/utils/scripts/bionet/mechanisms/modfiles/K_T.mod -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/bionet/mechanisms/modfiles
> copying bmtk/utils/scripts/bionet/mechanisms/modfiles/Kd.mod -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/bionet/mechanisms/modfiles
> copying bmtk/utils/scripts/bionet/mechanisms/modfiles/Kv2like.mod -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/bionet/mechanisms/modfiles
> copying bmtk/utils/scripts/bionet/mechanisms/modfiles/Kv3_1.mod -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/bionet/mechanisms/modfiles
> copying bmtk/utils/scripts/bionet/mechanisms/modfiles/NaTa.mod -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/bionet/mechanisms/modfiles
> copying bmtk/utils/scripts/bionet/mechanisms/modfiles/NaTs.mod -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/bionet/mechanisms/modfiles
> copying bmtk/utils/scripts/bionet/mechanisms/modfiles/NaV.mod -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/bionet/mechanisms/modfiles
> copying bmtk/utils/scripts/bionet/mechanisms/modfiles/Nap.mod -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/bionet/mechanisms/modfiles
> copying bmtk/utils/scripts/bionet/mechanisms/modfiles/SK.mod -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/bionet/mechanisms/modfiles
> copying bmtk/utils/scripts/bionet/mechanisms/modfiles/vecevent.mod -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/bionet/mechanisms/modfiles
> creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/bionet/morphologies
> copying bmtk/utils/scripts/bionet/morphologies/Nr5a1_471087815_m.swc -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/bionet/morphologies
> copying bmtk/utils/scripts/bionet/morphologies/Pvalb_469628681_m.swc -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/bionet/morphologies
> copying bmtk/utils/scripts/bionet/morphologies/Pvalb_470522102_m.swc -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/bionet/morphologies
> copying bmtk/utils/scripts/bionet/morphologies/Rorb_325404214_m.swc -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/bionet/morphologies
> copying bmtk/utils/scripts/bionet/morphologies/Scnn1a_473845048_m.swc -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/bionet/morphologies
> creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/bionet/point_neuron_models
> copying bmtk/utils/scripts/bionet/point_neuron_models/IntFire1_exc_1.json -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/bionet/point_neuron_models
> copying bmtk/utils/scripts/bionet/point_neuron_models/IntFire1_inh_1.json -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/bionet/point_neuron_models
> creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/bionet/synaptic_models
> copying bmtk/utils/scripts/bionet/synaptic_models/AMPA_ExcToExc.json -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/bionet/synaptic_models
> copying bmtk/utils/scripts/bionet/synaptic_models/AMPA_ExcToInh.json -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/bionet/synaptic_models
> copying bmtk/utils/scripts/bionet/synaptic_models/GABA_InhToExc.json -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/bionet/synaptic_models
> copying bmtk/utils/scripts/bionet/synaptic_models/GABA_InhToInh.json -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/bionet/synaptic_models
> copying bmtk/utils/scripts/bionet/synaptic_models/instantaneousExc.json -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/bionet/synaptic_models
> copying bmtk/utils/scripts/bionet/synaptic_models/instantaneousInh.json -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/bionet/synaptic_models
> creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/bionet/templates
> copying bmtk/utils/scripts/bionet/templates/BioAllen_old.hoc -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/bionet/templates
> copying bmtk/utils/scripts/bionet/templates/BioAxonStub.hoc -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/bionet/templates
> copying bmtk/utils/scripts/bionet/templates/Biophys1.hoc -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/bionet/templates
> creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/filternet
> copying bmtk/utils/scripts/filternet/run_filternet.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/filternet
> creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/filternet/filter_models
> copying bmtk/utils/scripts/filternet/filter_models/sOFF_TF1.json -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/filternet/filter_models
> copying bmtk/utils/scripts/filternet/filter_models/sOFF_TF15.json -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/filternet/filter_models
> copying bmtk/utils/scripts/filternet/filter_models/sOFF_TF2.json -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/filternet/filter_models
> copying bmtk/utils/scripts/filternet/filter_models/sOFF_TF4.json -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/filternet/filter_models
> copying bmtk/utils/scripts/filternet/filter_models/sOFF_TF8.json -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/filternet/filter_models
> copying bmtk/utils/scripts/filternet/filter_models/sON_TF1.json -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/filternet/filter_models
> copying bmtk/utils/scripts/filternet/filter_models/sON_TF2.json -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/filternet/filter_models
> copying bmtk/utils/scripts/filternet/filter_models/sON_TF4.json -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/filternet/filter_models
> copying bmtk/utils/scripts/filternet/filter_models/sON_TF8.json -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/filternet/filter_models
> copying bmtk/utils/scripts/filternet/filter_models/tOFF_TF15.json -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/filternet/filter_models
> copying bmtk/utils/scripts/filternet/filter_models/tOFF_TF4.json -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/filternet/filter_models
> copying bmtk/utils/scripts/filternet/filter_models/tOFF_TF8.json -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/filternet/filter_models
> creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/pointnet
> copying bmtk/utils/scripts/pointnet/run_pointnet.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/pointnet
> creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/pointnet/filter_models
> copying bmtk/utils/scripts/pointnet/filter_models/sOFF_TF1.json -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/pointnet/filter_models
> copying bmtk/utils/scripts/pointnet/filter_models/sOFF_TF15.json -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/pointnet/filter_models
> copying bmtk/utils/scripts/pointnet/filter_models/sOFF_TF2.json -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/pointnet/filter_models
> copying bmtk/utils/scripts/pointnet/filter_models/sOFF_TF4.json -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/pointnet/filter_models
> copying bmtk/utils/scripts/pointnet/filter_models/sOFF_TF8.json -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/pointnet/filter_models
> copying bmtk/utils/scripts/pointnet/filter_models/sON_TF1.json -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/pointnet/filter_models
> copying bmtk/utils/scripts/pointnet/filter_models/sON_TF2.json -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/pointnet/filter_models
> copying bmtk/utils/scripts/pointnet/filter_models/sON_TF4.json -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/pointnet/filter_models
> copying bmtk/utils/scripts/pointnet/filter_models/sON_TF8.json -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/pointnet/filter_models
> copying bmtk/utils/scripts/pointnet/filter_models/tOFF_TF15.json -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/pointnet/filter_models
> copying bmtk/utils/scripts/pointnet/filter_models/tOFF_TF4.json -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/pointnet/filter_models
> copying bmtk/utils/scripts/pointnet/filter_models/tOFF_TF8.json -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/pointnet/filter_models
> creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/pointnet/point_neuron_models
> copying bmtk/utils/scripts/pointnet/point_neuron_models/472363762_point.json -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/pointnet/point_neuron_models
> copying bmtk/utils/scripts/pointnet/point_neuron_models/472912177_point.json -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/pointnet/point_neuron_models
> copying bmtk/utils/scripts/pointnet/point_neuron_models/473862421_point.json -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/pointnet/point_neuron_models
> copying bmtk/utils/scripts/pointnet/point_neuron_models/473863035_point.json -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/pointnet/point_neuron_models
> copying bmtk/utils/scripts/pointnet/point_neuron_models/473863510_point.json -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/pointnet/point_neuron_models
> copying bmtk/utils/scripts/pointnet/point_neuron_models/IntFire1_exc_point.json -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/pointnet/point_neuron_models
> copying bmtk/utils/scripts/pointnet/point_neuron_models/IntFire1_inh_point.json -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/pointnet/point_neuron_models
> copying bmtk/utils/scripts/pointnet/point_neuron_models/filter_point.json -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/pointnet/point_neuron_models
> creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/pointnet/synaptic_models
> copying bmtk/utils/scripts/pointnet/synaptic_models/ExcToExc.json -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/pointnet/synaptic_models
> copying bmtk/utils/scripts/pointnet/synaptic_models/ExcToInh.json -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/pointnet/synaptic_models
> copying bmtk/utils/scripts/pointnet/synaptic_models/InhToExc.json -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/pointnet/synaptic_models
> copying bmtk/utils/scripts/pointnet/synaptic_models/InhToInh.json -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/pointnet/synaptic_models
> copying bmtk/utils/scripts/pointnet/synaptic_models/instantaneousExc.json -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/pointnet/synaptic_models
> copying bmtk/utils/scripts/pointnet/synaptic_models/instantaneousInh.json -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/pointnet/synaptic_models
> creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/popnet
> copying bmtk/utils/scripts/popnet/run_popnet.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/popnet
> creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/popnet/population_models
> copying bmtk/utils/scripts/popnet/population_models/exc_model.json -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/popnet/population_models
> copying bmtk/utils/scripts/popnet/population_models/inh_model.json -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/popnet/population_models
> creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/popnet/synaptic_models
> copying bmtk/utils/scripts/popnet/synaptic_models/ExcToExc.json -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/popnet/synaptic_models
> copying bmtk/utils/scripts/popnet/synaptic_models/ExcToInh.json -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/popnet/synaptic_models
> copying bmtk/utils/scripts/popnet/synaptic_models/InhToExc.json -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/popnet/synaptic_models
> copying bmtk/utils/scripts/popnet/synaptic_models/InhToInh.json -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/popnet/synaptic_models
> copying bmtk/utils/scripts/popnet/synaptic_models/input_ExcToExc.json -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/popnet/synaptic_models
> copying bmtk/utils/scripts/popnet/synaptic_models/input_ExcToInh.json -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/scripts/popnet/synaptic_models
> copying bmtk/simulator/bionet/README.md -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/bionet
> copying bmtk/simulator/bionet/import3d.hoc -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/bionet
> creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/bionet/default_templates
> copying bmtk/simulator/bionet/default_templates/BioAxonStub.hoc -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/bionet/default_templates
> copying bmtk/simulator/bionet/default_templates/Biophys1.hoc -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/bionet/default_templates
> copying bmtk/simulator/bionet/default_templates/advance.hoc -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/bionet/default_templates
> creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/bionet/import3d
> copying bmtk/simulator/bionet/import3d/import3d_gui.hoc -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/bionet/import3d
> copying bmtk/simulator/bionet/import3d/import3d_sec.hoc -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/bionet/import3d
> copying bmtk/simulator/bionet/import3d/read_morphml.hoc -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/bionet/import3d
> copying bmtk/simulator/bionet/import3d/read_nlcda.hoc -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/bionet/import3d
> copying bmtk/simulator/bionet/import3d/read_nlcda3.hoc -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/bionet/import3d
> copying bmtk/simulator/bionet/import3d/read_nts.hoc -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/bionet/import3d
> copying bmtk/simulator/bionet/import3d/read_swc.hoc -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/bionet/import3d
> creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/bionet/schemas
> copying bmtk/simulator/bionet/schemas/config_schema.json -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/bionet/schemas
> copying bmtk/simulator/bionet/schemas/csv_edge_types.json -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/bionet/schemas
> copying bmtk/simulator/bionet/schemas/csv_node_types_external.json -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/bionet/schemas
> copying bmtk/simulator/bionet/schemas/csv_node_types_internal.json -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/bionet/schemas
> copying bmtk/simulator/bionet/schemas/csv_nodes_external.json -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/bionet/schemas
> copying bmtk/simulator/bionet/schemas/csv_nodes_internal.json -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/bionet/schemas
> creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/filternet/lgnmodel/cell_metrics
> copying bmtk/simulator/filternet/lgnmodel/cell_metrics/sOFF_cell_data.csv -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/filternet/lgnmodel/cell_metrics
> copying bmtk/simulator/filternet/lgnmodel/cell_metrics/sON_cell_data.csv -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/filternet/lgnmodel/cell_metrics
> copying bmtk/simulator/filternet/lgnmodel/cell_metrics/sus_sus_cells_v3.csv -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/filternet/lgnmodel/cell_metrics
> copying bmtk/simulator/filternet/lgnmodel/cell_metrics/tOFF_cell_data.csv -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/filternet/lgnmodel/cell_metrics
> copying bmtk/simulator/filternet/lgnmodel/cell_metrics/tON_cell_data.csv -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/filternet/lgnmodel/cell_metrics
> copying bmtk/simulator/filternet/lgnmodel/cell_metrics/trans_sus_cells_v3.csv -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/filternet/lgnmodel/cell_metrics
> copying bmtk/utils/sonata/config/config_schema.json -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/sonata/config
> sphinx-apidoc -f -o docs/autodocs/source/bmtk/ bmtk
> Creating file docs/autodocs/source/bmtk/bmtk.rst.
> Creating file docs/autodocs/source/bmtk/bmtk.analyzer.rst.
> Creating file docs/autodocs/source/bmtk/bmtk.builder.rst.
> Creating file docs/autodocs/source/bmtk/bmtk.builder.auxi.rst.
> Creating file docs/autodocs/source/bmtk/bmtk.builder.bionet.rst.
> Creating file docs/autodocs/source/bmtk/bmtk.builder.edges_sorter.rst.
> Creating file docs/autodocs/source/bmtk/bmtk.builder.network_adaptors.rst.
> Creating file docs/autodocs/source/bmtk/bmtk.simulator.rst.
> Creating file docs/autodocs/source/bmtk/bmtk.simulator.bionet.rst.
> Creating file docs/autodocs/source/bmtk/bmtk.simulator.bionet.default_setters.rst.
> Creating file docs/autodocs/source/bmtk/bmtk.simulator.bionet.modules.rst.
> Creating file docs/autodocs/source/bmtk/bmtk.simulator.filternet.rst.
> Creating file docs/autodocs/source/bmtk/bmtk.simulator.filternet.default_setters.rst.
> Creating file docs/autodocs/source/bmtk/bmtk.simulator.filternet.lgnmodel.rst.
> Creating file docs/autodocs/source/bmtk/bmtk.simulator.filternet.modules.rst.
> Creating file docs/autodocs/source/bmtk/bmtk.simulator.pointnet.rst.
> Creating file docs/autodocs/source/bmtk/bmtk.simulator.pointnet.default_setters.rst.
> Creating file docs/autodocs/source/bmtk/bmtk.simulator.pointnet.modules.rst.
> Creating file docs/autodocs/source/bmtk/bmtk.simulator.popnet.rst.
> Creating file docs/autodocs/source/bmtk/bmtk.simulator.utils.rst.
> Creating file docs/autodocs/source/bmtk/bmtk.utils.rst.
> Creating file docs/autodocs/source/bmtk/bmtk.utils.compile_mechanisms.rst.
> Creating file docs/autodocs/source/bmtk/bmtk.utils.create_environment.rst.
> Creating file docs/autodocs/source/bmtk/bmtk.utils.io.rst.
> Creating file docs/autodocs/source/bmtk/bmtk.utils.reports.rst.
> Creating file docs/autodocs/source/bmtk/bmtk.utils.reports.compartment.rst.
> Creating file docs/autodocs/source/bmtk/bmtk.utils.reports.spike_trains.rst.
> Creating file docs/autodocs/source/bmtk/bmtk.utils.sonata.rst.
> Creating file docs/autodocs/source/bmtk/bmtk.utils.sonata.config.rst.
> Creating file docs/autodocs/source/bmtk/modules.rst.
> PYTHONPATH=. python3 -m sphinx -N -bhtml docs/autodocs/source/ build/html # HTML generator
> Running Sphinx v5.3.0
> WARNING: Invalid configuration value found: 'language = None'. Update your configuration to a valid language code. Falling back to 'en' (English).
> making output directory... done
> WARNING: html_extra_path entry '../.nojekyll' does not exist
> WARNING: html_static_path entry '/usr/share/javascript/requirejs/require.min.js' does not exist
> [autosummary] generating autosummary for: analyzer.rst, bionet.rst, bionet_config.rst, bionet_tutorial.rst, bmtk/bmtk.analyzer.rst, bmtk/bmtk.builder.auxi.rst, bmtk/bmtk.builder.bionet.rst, bmtk/bmtk.builder.edges_sorter.rst, bmtk/bmtk.builder.network_adaptors.rst, bmtk/bmtk.builder.rst, ..., simulators.rst, tutorial_NetworkBuilder_Intro.ipynb, tutorial_filter_models.ipynb, tutorial_multi_pop.ipynb, tutorial_pointnet_modeling.ipynb, tutorial_population_modeling.ipynb, tutorial_single_cell_clamped.ipynb, tutorial_single_cell_syn.ipynb, tutorial_single_pop.ipynb, tutorials.rst
> Matplotlib created a temporary config/cache directory at /tmp/matplotlib-tu5cozas because the default path (/home/user42/.config/matplotlib) is not a writable directory; it is highly recommended to set the MPLCONFIGDIR environment variable to a writable directory, in particular to speed up the import of Matplotlib and to better support multiprocessing.
> numprocs=1
> Failed to import bmtk.simulator.popnet.config.
> Possible hints:
> * AttributeError: module 'bmtk.simulator' has no attribute 'popnet'
> * ModuleNotFoundError: No module named 'dipde'
> Failed to import bmtk.simulator.popnet.popedge.
> Possible hints:
> * AttributeError: module 'bmtk.simulator' has no attribute 'popnet'
> * ModuleNotFoundError: No module named 'dipde'
> Failed to import bmtk.simulator.popnet.popnetwork.
> Possible hints:
> * AttributeError: module 'bmtk.simulator' has no attribute 'popnet'
> * ModuleNotFoundError: No module named 'dipde'
> Failed to import bmtk.simulator.popnet.popnode.
> Possible hints:
> * AttributeError: module 'bmtk.simulator' has no attribute 'popnet'
> * ModuleNotFoundError: No module named 'dipde'
> Failed to import bmtk.simulator.popnet.popsimulator.
> Possible hints:
> * AttributeError: module 'bmtk.simulator' has no attribute 'popnet'
> * ModuleNotFoundError: No module named 'dipde'
> Failed to import bmtk.simulator.popnet.
> Possible hints:
> * AttributeError: module 'bmtk.simulator' has no attribute 'popnet'
> * ModuleNotFoundError: No module named 'dipde'
> building [mo]: targets for 0 po files that are out of date
> building [html]: targets for 61 source files that are out of date
> updating environment: [new config] 61 added, 0 changed, 0 removed
> reading sources... [  1%] analyzer
> reading sources... [  3%] bionet
> reading sources... [  4%] bionet_config
> reading sources... [  6%] bionet_tutorial
> reading sources... [  8%] bmtk/bmtk
> reading sources... [  9%] bmtk/bmtk.analyzer
> reading sources... [ 11%] bmtk/bmtk.builder
> reading sources... [ 13%] bmtk/bmtk.builder.auxi
> reading sources... [ 14%] bmtk/bmtk.builder.bionet
> reading sources... [ 16%] bmtk/bmtk.builder.edges_sorter
> reading sources... [ 18%] bmtk/bmtk.builder.network_adaptors
> reading sources... [ 19%] bmtk/bmtk.simulator
> reading sources... [ 21%] bmtk/bmtk.simulator.bionet
> reading sources... [ 22%] bmtk/bmtk.simulator.bionet.default_setters
> reading sources... [ 24%] bmtk/bmtk.simulator.bionet.modules
> reading sources... [ 26%] bmtk/bmtk.simulator.core
> reading sources... [ 27%] bmtk/bmtk.simulator.core.sonata_reader
> reading sources... [ 29%] bmtk/bmtk.simulator.filternet
> reading sources... [ 31%] bmtk/bmtk.simulator.filternet.default_setters
> reading sources... [ 32%] bmtk/bmtk.simulator.filternet.lgnmodel
> reading sources... [ 34%] bmtk/bmtk.simulator.filternet.modules
> reading sources... [ 36%] bmtk/bmtk.simulator.pointnet
> reading sources... [ 37%] bmtk/bmtk.simulator.pointnet.default_setters
> reading sources... [ 39%] bmtk/bmtk.simulator.pointnet.modules
> reading sources... [ 40%] bmtk/bmtk.simulator.popnet
> reading sources... [ 42%] bmtk/bmtk.simulator.utils
> reading sources... [ 44%] bmtk/bmtk.tests
> reading sources... [ 45%] bmtk/bmtk.tests.simulator
> reading sources... [ 47%] bmtk/bmtk.tests.simulator.bionet
> reading sources... [ 49%] bmtk/bmtk.tests.simulator.pointnet
> reading sources... [ 50%] bmtk/bmtk.tests.simulator.popnet
> reading sources... [ 52%] bmtk/bmtk.utils
> reading sources... [ 54%] bmtk/bmtk.utils.compile_mechanisms
> reading sources... [ 55%] bmtk/bmtk.utils.create_environment
> reading sources... [ 57%] bmtk/bmtk.utils.io
> reading sources... [ 59%] bmtk/bmtk.utils.reports
> reading sources... [ 60%] bmtk/bmtk.utils.reports.compartment
> reading sources... [ 62%] bmtk/bmtk.utils.reports.spike_trains
> reading sources... [ 63%] bmtk/bmtk.utils.sonata
> reading sources... [ 65%] bmtk/bmtk.utils.sonata.config
> reading sources... [ 67%] bmtk/modules
> reading sources... [ 68%] builder
> reading sources... [ 70%] contributors
> reading sources... [ 72%] examples
> reading sources... [ 73%] filternet
> reading sources... [ 75%] index
> reading sources... [ 77%] installation
> reading sources... [ 78%] network_file_formats
> reading sources... [ 80%] pointnet
> reading sources... [ 81%] popnet
> reading sources... [ 83%] registration
> reading sources... [ 85%] simulators
> reading sources... [ 86%] tutorial_NetworkBuilder_Intro
> reading sources... [ 88%] tutorial_filter_models
> reading sources... [ 90%] tutorial_multi_pop
> reading sources... [ 91%] tutorial_pointnet_modeling
> reading sources... [ 93%] tutorial_population_modeling
> reading sources... [ 95%] tutorial_single_cell_clamped
> reading sources... [ 96%] tutorial_single_cell_syn
> reading sources... [ 98%] tutorial_single_pop
> reading sources... [100%] tutorials
> 
> WARNING: autodoc: failed to import module 'popnet.config' from module 'bmtk.simulator'; the following exception was raised:
> No module named 'dipde'
> WARNING: autodoc: failed to import module 'popnet.popedge' from module 'bmtk.simulator'; the following exception was raised:
> No module named 'dipde'
> WARNING: autodoc: failed to import module 'popnet.popnetwork' from module 'bmtk.simulator'; the following exception was raised:
> No module named 'dipde'
> WARNING: autodoc: failed to import module 'popnet.popnode' from module 'bmtk.simulator'; the following exception was raised:
> No module named 'dipde'
> WARNING: autodoc: failed to import module 'popnet.popsimulator' from module 'bmtk.simulator'; the following exception was raised:
> No module named 'dipde'
> WARNING: autodoc: failed to import module 'popnet' from module 'bmtk.simulator'; the following exception was raised:
> No module named 'dipde'
> /<<PKGBUILDDIR>>/docs/autodocs/source/installation.rst:2: WARNING: Duplicate explicit target name: "here".
> looking for now-outdated files... none found
> pickling environment... done
> checking consistency... /<<PKGBUILDDIR>>/docs/autodocs/source/bmtk/bmtk.simulator.core.rst: WARNING: document isn't included in any toctree
> /<<PKGBUILDDIR>>/docs/autodocs/source/bmtk/bmtk.tests.rst: WARNING: document isn't included in any toctree
> /<<PKGBUILDDIR>>/docs/autodocs/source/bmtk/modules.rst: WARNING: document isn't included in any toctree
> done
> preparing documents... done
> writing output... [  1%] analyzer
> writing output... [  3%] bionet
> writing output... [  4%] bionet_config
> writing output... [  6%] bionet_tutorial
> writing output... [  8%] bmtk/bmtk
> writing output... [  9%] bmtk/bmtk.analyzer
> writing output... [ 11%] bmtk/bmtk.builder
> writing output... [ 13%] bmtk/bmtk.builder.auxi
> writing output... [ 14%] bmtk/bmtk.builder.bionet
> writing output... [ 16%] bmtk/bmtk.builder.edges_sorter
> writing output... [ 18%] bmtk/bmtk.builder.network_adaptors
> writing output... [ 19%] bmtk/bmtk.simulator
> writing output... [ 21%] bmtk/bmtk.simulator.bionet
> writing output... [ 22%] bmtk/bmtk.simulator.bionet.default_setters
> writing output... [ 24%] bmtk/bmtk.simulator.bionet.modules
> writing output... [ 26%] bmtk/bmtk.simulator.core
> writing output... [ 27%] bmtk/bmtk.simulator.core.sonata_reader
> writing output... [ 29%] bmtk/bmtk.simulator.filternet
> writing output... [ 31%] bmtk/bmtk.simulator.filternet.default_setters
> writing output... [ 32%] bmtk/bmtk.simulator.filternet.lgnmodel
> writing output... [ 34%] bmtk/bmtk.simulator.filternet.modules
> writing output... [ 36%] bmtk/bmtk.simulator.pointnet
> writing output... [ 37%] bmtk/bmtk.simulator.pointnet.default_setters
> writing output... [ 39%] bmtk/bmtk.simulator.pointnet.modules
> writing output... [ 40%] bmtk/bmtk.simulator.popnet
> writing output... [ 42%] bmtk/bmtk.simulator.utils
> writing output... [ 44%] bmtk/bmtk.tests
> writing output... [ 45%] bmtk/bmtk.tests.simulator
> writing output... [ 47%] bmtk/bmtk.tests.simulator.bionet
> writing output... [ 49%] bmtk/bmtk.tests.simulator.pointnet
> writing output... [ 50%] bmtk/bmtk.tests.simulator.popnet
> writing output... [ 52%] bmtk/bmtk.utils
> writing output... [ 54%] bmtk/bmtk.utils.compile_mechanisms
> writing output... [ 55%] bmtk/bmtk.utils.create_environment
> writing output... [ 57%] bmtk/bmtk.utils.io
> writing output... [ 59%] bmtk/bmtk.utils.reports
> writing output... [ 60%] bmtk/bmtk.utils.reports.compartment
> writing output... [ 62%] bmtk/bmtk.utils.reports.spike_trains
> writing output... [ 63%] bmtk/bmtk.utils.sonata
> writing output... [ 65%] bmtk/bmtk.utils.sonata.config
> writing output... [ 67%] bmtk/modules
> writing output... [ 68%] builder
> writing output... [ 70%] contributors
> writing output... [ 72%] examples
> writing output... [ 73%] filternet
> writing output... [ 75%] index
> writing output... [ 77%] installation
> writing output... [ 78%] network_file_formats
> writing output... [ 80%] pointnet
> writing output... [ 81%] popnet
> writing output... [ 83%] registration
> writing output... [ 85%] simulators
> writing output... [ 86%] tutorial_NetworkBuilder_Intro
> writing output... [ 88%] tutorial_filter_models
> writing output... [ 90%] tutorial_multi_pop
> writing output... [ 91%] tutorial_pointnet_modeling
> writing output... [ 93%] tutorial_population_modeling
> writing output... [ 95%] tutorial_single_cell_clamped
> writing output... [ 96%] tutorial_single_cell_syn
> writing output... [ 98%] tutorial_single_pop
> writing output... [100%] tutorials
> 
> /<<PKGBUILDDIR>>/docs/autodocs/source/bionet.rst:405: WARNING: Could not lex literal_block as "json". Highlighting skipped.
> /<<PKGBUILDDIR>>/docs/autodocs/source/tutorial_NetworkBuilder_Intro.ipynb:: WARNING: Pygments lexer name 'ipython3' is not known
> /<<PKGBUILDDIR>>/docs/autodocs/source/tutorial_NetworkBuilder_Intro.ipynb:: WARNING: Pygments lexer name 'ipython3' is not known
> /<<PKGBUILDDIR>>/docs/autodocs/source/tutorial_NetworkBuilder_Intro.ipynb:: WARNING: Pygments lexer name 'ipython3' is not known
> /<<PKGBUILDDIR>>/docs/autodocs/source/tutorial_NetworkBuilder_Intro.ipynb:: WARNING: Pygments lexer name 'ipython3' is not known
> /<<PKGBUILDDIR>>/docs/autodocs/source/tutorial_NetworkBuilder_Intro.ipynb:: WARNING: Pygments lexer name 'ipython3' is not known
> /<<PKGBUILDDIR>>/docs/autodocs/source/tutorial_NetworkBuilder_Intro.ipynb:: WARNING: Pygments lexer name 'ipython3' is not known
> /<<PKGBUILDDIR>>/docs/autodocs/source/tutorial_NetworkBuilder_Intro.ipynb:: WARNING: Pygments lexer name 'ipython3' is not known
> /<<PKGBUILDDIR>>/docs/autodocs/source/tutorial_NetworkBuilder_Intro.ipynb:: WARNING: Pygments lexer name 'ipython3' is not known
> /<<PKGBUILDDIR>>/docs/autodocs/source/tutorial_NetworkBuilder_Intro.ipynb:: WARNING: Pygments lexer name 'ipython3' is not known
> /<<PKGBUILDDIR>>/docs/autodocs/source/tutorial_NetworkBuilder_Intro.ipynb:: WARNING: Pygments lexer name 'ipython3' is not known
> /<<PKGBUILDDIR>>/docs/autodocs/source/tutorial_filter_models.ipynb:: WARNING: Pygments lexer name 'ipython3' is not known
> /<<PKGBUILDDIR>>/docs/autodocs/source/tutorial_filter_models.ipynb:: WARNING: Pygments lexer name 'ipython3' is not known
> /<<PKGBUILDDIR>>/docs/autodocs/source/tutorial_filter_models.ipynb:: WARNING: Pygments lexer name 'ipython3' is not known
> /<<PKGBUILDDIR>>/docs/autodocs/source/tutorial_filter_models.ipynb:: WARNING: Pygments lexer name 'ipython3' is not known
> /<<PKGBUILDDIR>>/docs/autodocs/source/tutorial_filter_models.ipynb:: WARNING: Pygments lexer name 'ipython3' is not known
> /<<PKGBUILDDIR>>/docs/autodocs/source/tutorial_multi_pop.ipynb:: WARNING: Pygments lexer name 'ipython3' is not known
> /<<PKGBUILDDIR>>/docs/autodocs/source/tutorial_multi_pop.ipynb:: WARNING: Pygments lexer name 'ipython3' is not known
> /<<PKGBUILDDIR>>/docs/autodocs/source/tutorial_multi_pop.ipynb:: WARNING: Pygments lexer name 'ipython3' is not known
> /<<PKGBUILDDIR>>/docs/autodocs/source/tutorial_multi_pop.ipynb:: WARNING: Pygments lexer name 'ipython3' is not known
> /<<PKGBUILDDIR>>/docs/autodocs/source/tutorial_multi_pop.ipynb:: WARNING: Pygments lexer name 'ipython3' is not known
> /<<PKGBUILDDIR>>/docs/autodocs/source/tutorial_multi_pop.ipynb:: WARNING: Pygments lexer name 'ipython3' is not known
> /<<PKGBUILDDIR>>/docs/autodocs/source/tutorial_multi_pop.ipynb:: WARNING: Pygments lexer name 'ipython3' is not known
> /<<PKGBUILDDIR>>/docs/autodocs/source/tutorial_multi_pop.ipynb:: WARNING: Pygments lexer name 'ipython3' is not known
> /<<PKGBUILDDIR>>/docs/autodocs/source/tutorial_multi_pop.ipynb:: WARNING: Pygments lexer name 'ipython3' is not known
> /<<PKGBUILDDIR>>/docs/autodocs/source/tutorial_multi_pop.ipynb:: WARNING: Pygments lexer name 'ipython3' is not known
> /<<PKGBUILDDIR>>/docs/autodocs/source/tutorial_multi_pop.ipynb:: WARNING: Pygments lexer name 'ipython3' is not known
> /<<PKGBUILDDIR>>/docs/autodocs/source/tutorial_multi_pop.ipynb:: WARNING: Pygments lexer name 'ipython3' is not known
> /<<PKGBUILDDIR>>/docs/autodocs/source/tutorial_multi_pop.ipynb:: WARNING: Pygments lexer name 'ipython3' is not known
> /<<PKGBUILDDIR>>/docs/autodocs/source/tutorial_multi_pop.ipynb:: WARNING: Pygments lexer name 'ipython3' is not known
> /<<PKGBUILDDIR>>/docs/autodocs/source/tutorial_multi_pop.ipynb:: WARNING: Pygments lexer name 'ipython3' is not known
> /<<PKGBUILDDIR>>/docs/autodocs/source/tutorial_pointnet_modeling.ipynb:: WARNING: Pygments lexer name 'ipython3' is not known
> /<<PKGBUILDDIR>>/docs/autodocs/source/tutorial_pointnet_modeling.ipynb:: WARNING: Pygments lexer name 'ipython3' is not known
> /<<PKGBUILDDIR>>/docs/autodocs/source/tutorial_pointnet_modeling.ipynb:: WARNING: Pygments lexer name 'ipython3' is not known
> /<<PKGBUILDDIR>>/docs/autodocs/source/tutorial_pointnet_modeling.ipynb:: WARNING: Pygments lexer name 'ipython3' is not known
> /<<PKGBUILDDIR>>/docs/autodocs/source/tutorial_pointnet_modeling.ipynb:: WARNING: Pygments lexer name 'ipython3' is not known
> /<<PKGBUILDDIR>>/docs/autodocs/source/tutorial_pointnet_modeling.ipynb:: WARNING: Pygments lexer name 'ipython3' is not known
> /<<PKGBUILDDIR>>/docs/autodocs/source/tutorial_pointnet_modeling.ipynb:: WARNING: Pygments lexer name 'ipython3' is not known
> /<<PKGBUILDDIR>>/docs/autodocs/source/tutorial_pointnet_modeling.ipynb:: WARNING: Pygments lexer name 'ipython3' is not known
> /<<PKGBUILDDIR>>/docs/autodocs/source/tutorial_pointnet_modeling.ipynb:: WARNING: Pygments lexer name 'ipython3' is not known
> /<<PKGBUILDDIR>>/docs/autodocs/source/tutorial_pointnet_modeling.ipynb:: WARNING: Pygments lexer name 'ipython3' is not known
> /<<PKGBUILDDIR>>/docs/autodocs/source/tutorial_pointnet_modeling.ipynb:: WARNING: Pygments lexer name 'ipython3' is not known
> /<<PKGBUILDDIR>>/docs/autodocs/source/tutorial_pointnet_modeling.ipynb:: WARNING: Pygments lexer name 'ipython3' is not known
> /<<PKGBUILDDIR>>/docs/autodocs/source/tutorial_pointnet_modeling.ipynb:: WARNING: Pygments lexer name 'ipython3' is not known
> /<<PKGBUILDDIR>>/docs/autodocs/source/tutorial_pointnet_modeling.ipynb:: WARNING: Pygments lexer name 'ipython3' is not known
> /<<PKGBUILDDIR>>/docs/autodocs/source/tutorial_population_modeling.ipynb:: WARNING: Pygments lexer name 'ipython3' is not known
> /<<PKGBUILDDIR>>/docs/autodocs/source/tutorial_population_modeling.ipynb:: WARNING: Pygments lexer name 'ipython3' is not known
> /<<PKGBUILDDIR>>/docs/autodocs/source/tutorial_population_modeling.ipynb:: WARNING: Pygments lexer name 'ipython3' is not known
> /<<PKGBUILDDIR>>/docs/autodocs/source/tutorial_population_modeling.ipynb:: WARNING: Pygments lexer name 'ipython3' is not known
> /<<PKGBUILDDIR>>/docs/autodocs/source/tutorial_population_modeling.ipynb:: WARNING: Pygments lexer name 'ipython3' is not known
> /<<PKGBUILDDIR>>/docs/autodocs/source/tutorial_population_modeling.ipynb:: WARNING: Pygments lexer name 'ipython3' is not known
> /<<PKGBUILDDIR>>/docs/autodocs/source/tutorial_population_modeling.ipynb:: WARNING: Pygments lexer name 'ipython3' is not known
> /<<PKGBUILDDIR>>/docs/autodocs/source/tutorial_population_modeling.ipynb:: WARNING: Pygments lexer name 'ipython3' is not known
> /<<PKGBUILDDIR>>/docs/autodocs/source/tutorial_population_modeling.ipynb:: WARNING: Pygments lexer name 'ipython3' is not known
> /<<PKGBUILDDIR>>/docs/autodocs/source/tutorial_single_cell_clamped.ipynb:: WARNING: Pygments lexer name 'ipython3' is not known
> /<<PKGBUILDDIR>>/docs/autodocs/source/tutorial_single_cell_clamped.ipynb:: WARNING: Pygments lexer name 'ipython3' is not known
> /<<PKGBUILDDIR>>/docs/autodocs/source/tutorial_single_cell_clamped.ipynb:: WARNING: Pygments lexer name 'ipython3' is not known
> /<<PKGBUILDDIR>>/docs/autodocs/source/tutorial_single_cell_clamped.ipynb:: WARNING: Pygments lexer name 'ipython3' is not known
> /<<PKGBUILDDIR>>/docs/autodocs/source/tutorial_single_cell_clamped.ipynb:: WARNING: Pygments lexer name 'ipython3' is not known
> /<<PKGBUILDDIR>>/docs/autodocs/source/tutorial_single_cell_clamped.ipynb:: WARNING: Pygments lexer name 'ipython3' is not known
> /<<PKGBUILDDIR>>/docs/autodocs/source/tutorial_single_cell_clamped.ipynb:: WARNING: Pygments lexer name 'ipython3' is not known
> /<<PKGBUILDDIR>>/docs/autodocs/source/tutorial_single_cell_clamped.ipynb:: WARNING: Pygments lexer name 'ipython3' is not known
> /<<PKGBUILDDIR>>/docs/autodocs/source/tutorial_single_cell_syn.ipynb:: WARNING: Pygments lexer name 'ipython3' is not known
> /<<PKGBUILDDIR>>/docs/autodocs/source/tutorial_single_cell_syn.ipynb:: WARNING: Pygments lexer name 'ipython3' is not known
> /<<PKGBUILDDIR>>/docs/autodocs/source/tutorial_single_cell_syn.ipynb:: WARNING: Pygments lexer name 'ipython3' is not known
> /<<PKGBUILDDIR>>/docs/autodocs/source/tutorial_single_cell_syn.ipynb:: WARNING: Pygments lexer name 'ipython3' is not known
> /<<PKGBUILDDIR>>/docs/autodocs/source/tutorial_single_cell_syn.ipynb:: WARNING: Pygments lexer name 'ipython3' is not known
> /<<PKGBUILDDIR>>/docs/autodocs/source/tutorial_single_cell_syn.ipynb:: WARNING: Pygments lexer name 'ipython3' is not known
> /<<PKGBUILDDIR>>/docs/autodocs/source/tutorial_single_cell_syn.ipynb:: WARNING: Pygments lexer name 'ipython3' is not known
> /<<PKGBUILDDIR>>/docs/autodocs/source/tutorial_single_cell_syn.ipynb:: WARNING: Pygments lexer name 'ipython3' is not known
> /<<PKGBUILDDIR>>/docs/autodocs/source/tutorial_single_cell_syn.ipynb:: WARNING: Pygments lexer name 'ipython3' is not known
> /<<PKGBUILDDIR>>/docs/autodocs/source/tutorial_single_cell_syn.ipynb:: WARNING: Pygments lexer name 'ipython3' is not known
> /<<PKGBUILDDIR>>/docs/autodocs/source/tutorial_single_cell_syn.ipynb:: WARNING: Pygments lexer name 'ipython3' is not known
> /<<PKGBUILDDIR>>/docs/autodocs/source/tutorial_single_cell_syn.ipynb:: WARNING: Pygments lexer name 'ipython3' is not known
> /<<PKGBUILDDIR>>/docs/autodocs/source/tutorial_single_cell_syn.ipynb:: WARNING: Pygments lexer name 'ipython3' is not known
> /<<PKGBUILDDIR>>/docs/autodocs/source/tutorial_single_pop.ipynb:: WARNING: Pygments lexer name 'ipython3' is not known
> /<<PKGBUILDDIR>>/docs/autodocs/source/tutorial_single_pop.ipynb:: WARNING: Pygments lexer name 'ipython3' is not known
> /<<PKGBUILDDIR>>/docs/autodocs/source/tutorial_single_pop.ipynb:: WARNING: Pygments lexer name 'ipython3' is not known
> /<<PKGBUILDDIR>>/docs/autodocs/source/tutorial_single_pop.ipynb:: WARNING: Pygments lexer name 'ipython3' is not known
> /<<PKGBUILDDIR>>/docs/autodocs/source/tutorial_single_pop.ipynb:: WARNING: Pygments lexer name 'ipython3' is not known
> /<<PKGBUILDDIR>>/docs/autodocs/source/tutorial_single_pop.ipynb:: WARNING: Pygments lexer name 'ipython3' is not known
> /<<PKGBUILDDIR>>/docs/autodocs/source/tutorial_single_pop.ipynb:: WARNING: Pygments lexer name 'ipython3' is not known
> /<<PKGBUILDDIR>>/docs/autodocs/source/tutorial_single_pop.ipynb:: WARNING: Pygments lexer name 'ipython3' is not known
> /<<PKGBUILDDIR>>/docs/autodocs/source/tutorial_single_pop.ipynb:: WARNING: Pygments lexer name 'ipython3' is not known
> /<<PKGBUILDDIR>>/docs/autodocs/source/tutorial_single_pop.ipynb:: WARNING: Pygments lexer name 'ipython3' is not known
> /<<PKGBUILDDIR>>/docs/autodocs/source/tutorial_single_pop.ipynb:: WARNING: Pygments lexer name 'ipython3' is not known
> /<<PKGBUILDDIR>>/docs/autodocs/source/tutorial_single_pop.ipynb:: WARNING: Pygments lexer name 'ipython3' is not known
> generating indices... genindex py-modindex done
> copying notebooks ... [ 12%] tutorial_NetworkBuilder_Intro.ipynb
> copying notebooks ... [ 25%] tutorial_filter_models.ipynb
> copying notebooks ... [ 37%] tutorial_multi_pop.ipynb
> copying notebooks ... [ 50%] tutorial_pointnet_modeling.ipynb
> copying notebooks ... [ 62%] tutorial_population_modeling.ipynb
> copying notebooks ... [ 75%] tutorial_single_cell_clamped.ipynb
> copying notebooks ... [ 87%] tutorial_single_cell_syn.ipynb
> copying notebooks ... [100%] tutorial_single_pop.ipynb
> 
> highlighting module code... [  0%] bmtk.analyzer
> highlighting module code... [  1%] bmtk.analyzer.compartment
> highlighting module code... [  1%] bmtk.analyzer.ecp
> highlighting module code... [  2%] bmtk.analyzer.firing_rates
> highlighting module code... [  2%] bmtk.analyzer.io_tools
> highlighting module code... [  3%] bmtk.analyzer.spike_trains
> highlighting module code... [  4%] bmtk.analyzer.spikes_analyzer
> highlighting module code... [  4%] bmtk.analyzer.spikes_loader
> highlighting module code... [  5%] bmtk.analyzer.utils
> highlighting module code... [  5%] bmtk.builder.auxi.edge_connectors
> highlighting module code... [  6%] bmtk.builder.auxi.node_params
> highlighting module code... [  6%] bmtk.builder.bionet
> highlighting module code... [  7%] bmtk.builder.bionet.swc_reader
> highlighting module code... [  8%] bmtk.builder.builder_utils
> highlighting module code... [  8%] bmtk.builder.connection_map
> highlighting module code... [  9%] bmtk.builder.connector
> highlighting module code... [  9%] bmtk.builder.edge
> highlighting module code... [ 10%] bmtk.builder.edges_sorter
> highlighting module code... [ 10%] bmtk.builder.edges_sorter.memory_sorter
> highlighting module code... [ 11%] bmtk.builder.edges_sorter.merge_sorter
> highlighting module code... [ 12%] bmtk.builder.functor_cache
> highlighting module code... [ 12%] bmtk.builder.id_generator
> highlighting module code... [ 13%] bmtk.builder.index_builders
> highlighting module code... [ 13%] bmtk.builder.iterator
> highlighting module code... [ 14%] bmtk.builder.network_adaptors.dm_network
> highlighting module code... [ 15%] bmtk.builder.network_adaptors.dm_network_orig
> highlighting module code... [ 15%] bmtk.builder.network_adaptors.edge_props_table
> highlighting module code... [ 16%] bmtk.builder.network_adaptors.edges_collator
> highlighting module code... [ 16%] bmtk.builder.network_adaptors.network
> highlighting module code... [ 17%] bmtk.builder.network_adaptors.nxnetwork
> highlighting module code... [ 17%] bmtk.builder.network_builder
> highlighting module code... [ 18%] bmtk.builder.node
> highlighting module code... [ 19%] bmtk.builder.node_pool
> highlighting module code... [ 19%] bmtk.builder.node_set
> highlighting module code... [ 20%] bmtk.simulator.bionet.biocell
> highlighting module code... [ 20%] bmtk.simulator.bionet.bionetwork
> highlighting module code... [ 21%] bmtk.simulator.bionet.biosimulator
> highlighting module code... [ 21%] bmtk.simulator.bionet.cell
> highlighting module code... [ 22%] bmtk.simulator.bionet.config
> highlighting module code... [ 23%] bmtk.simulator.bionet.default_setters.cell_models
> highlighting module code... [ 23%] bmtk.simulator.bionet.default_setters.synapse_models
> highlighting module code... [ 24%] bmtk.simulator.bionet.default_setters.synaptic_weights
> highlighting module code... [ 24%] bmtk.simulator.bionet.gids
> highlighting module code... [ 25%] bmtk.simulator.bionet.iclamp
> highlighting module code... [ 26%] bmtk.simulator.bionet.io_tools
> highlighting module code... [ 26%] bmtk.simulator.bionet.modules.ecp
> highlighting module code... [ 27%] bmtk.simulator.bionet.modules.record_cellvars
> highlighting module code... [ 27%] bmtk.simulator.bionet.modules.record_clamp
> highlighting module code... [ 28%] bmtk.simulator.bionet.modules.record_netcons
> highlighting module code... [ 28%] bmtk.simulator.bionet.modules.record_spikes
> highlighting module code... [ 29%] bmtk.simulator.bionet.modules.save_synapses
> highlighting module code... [ 30%] bmtk.simulator.bionet.modules.sim_module
> highlighting module code... [ 30%] bmtk.simulator.bionet.modules.xstim
> highlighting module code... [ 31%] bmtk.simulator.bionet.modules.xstim_waveforms
> highlighting module code... [ 31%] bmtk.simulator.bionet.morphology
> highlighting module code... [ 32%] bmtk.simulator.bionet.nml_reader
> highlighting module code... [ 32%] bmtk.simulator.bionet.nrn
> highlighting module code... [ 33%] bmtk.simulator.bionet.pointprocesscell
> highlighting module code... [ 34%] bmtk.simulator.bionet.pointsomacell
> highlighting module code... [ 34%] bmtk.simulator.bionet.seclamp
> highlighting module code... [ 35%] bmtk.simulator.bionet.sonata_adaptors
> highlighting module code... [ 35%] bmtk.simulator.bionet.utils
> highlighting module code... [ 36%] bmtk.simulator.bionet.virtualcell
> highlighting module code... [ 36%] bmtk.simulator.core.edge_population
> highlighting module code... [ 37%] bmtk.simulator.core.graph
> highlighting module code... [ 38%] bmtk.simulator.core.io_tools
> highlighting module code... [ 38%] bmtk.simulator.core.network_reader
> highlighting module code... [ 39%] bmtk.simulator.core.node_population
> highlighting module code... [ 39%] bmtk.simulator.core.node_sets
> highlighting module code... [ 40%] bmtk.simulator.core.pyfunction_cache
> highlighting module code... [ 41%] bmtk.simulator.core.simulation_config
> highlighting module code... [ 41%] bmtk.simulator.core.simulation_config_validator
> highlighting module code... [ 42%] bmtk.simulator.core.simulator
> highlighting module code... [ 42%] bmtk.simulator.core.simulator_network
> highlighting module code... [ 43%] bmtk.simulator.core.sonata_reader.edge_adaptor
> highlighting module code... [ 43%] bmtk.simulator.core.sonata_reader.network_reader
> highlighting module code... [ 44%] bmtk.simulator.core.sonata_reader.node_adaptor
> highlighting module code... [ 45%] bmtk.simulator.filternet.cell
> highlighting module code... [ 45%] bmtk.simulator.filternet.config
> highlighting module code... [ 46%] bmtk.simulator.filternet.default_setters.cell_loaders
> highlighting module code... [ 46%] bmtk.simulator.filternet.filternetwork
> highlighting module code... [ 47%] bmtk.simulator.filternet.filtersimulator
> highlighting module code... [ 47%] bmtk.simulator.filternet.io_tools
> highlighting module code... [ 48%] bmtk.simulator.filternet.lgnmodel.cellmetrics
> highlighting module code... [ 49%] bmtk.simulator.filternet.lgnmodel.cellmodel
> highlighting module code... [ 49%] bmtk.simulator.filternet.lgnmodel.cursor
> highlighting module code... [ 50%] bmtk.simulator.filternet.lgnmodel.fitfuns
> highlighting module code... [ 50%] bmtk.simulator.filternet.lgnmodel.kernel
> highlighting module code... [ 51%] bmtk.simulator.filternet.lgnmodel.lattice_unit_constructor
> highlighting module code... [ 52%] bmtk.simulator.filternet.lgnmodel.lgnmodel1
> highlighting module code... [ 52%] bmtk.simulator.filternet.lgnmodel.linearfilter
> highlighting module code... [ 53%] bmtk.simulator.filternet.lgnmodel.lnunit
> highlighting module code... [ 53%] bmtk.simulator.filternet.lgnmodel.make_cell_list
> highlighting module code... [ 54%] bmtk.simulator.filternet.lgnmodel.movie
> highlighting module code... [ 54%] bmtk.simulator.filternet.lgnmodel.poissongeneration
> highlighting module code... [ 55%] bmtk.simulator.filternet.lgnmodel.spatialfilter
> highlighting module code... [ 56%] bmtk.simulator.filternet.lgnmodel.temporalfilter
> highlighting module code... [ 56%] bmtk.simulator.filternet.lgnmodel.transferfunction
> highlighting module code... [ 57%] bmtk.simulator.filternet.lgnmodel.util_fns
> highlighting module code... [ 57%] bmtk.simulator.filternet.lgnmodel.utilities
> highlighting module code... [ 58%] bmtk.simulator.filternet.modules.base
> highlighting module code... [ 58%] bmtk.simulator.filternet.modules.create_spikes
> highlighting module code... [ 59%] bmtk.simulator.filternet.modules.record_rates
> highlighting module code... [ 60%] bmtk.simulator.filternet.pyfunction_cache
> highlighting module code... [ 60%] bmtk.simulator.filternet.sonata_adaptors
> highlighting module code... [ 61%] bmtk.simulator.pointnet.config
> highlighting module code... [ 61%] bmtk.simulator.pointnet.default_setters.synapse_models
> highlighting module code... [ 62%] bmtk.simulator.pointnet.default_setters.synaptic_weights
> highlighting module code... [ 63%] bmtk.simulator.pointnet.gids
> highlighting module code... [ 63%] bmtk.simulator.pointnet.glif_utils
> highlighting module code... [ 64%] bmtk.simulator.pointnet.io_tools
> highlighting module code... [ 64%] bmtk.simulator.pointnet.modules.multimeter_reporter
> highlighting module code... [ 65%] bmtk.simulator.pointnet.modules.record_spikes
> highlighting module code... [ 65%] bmtk.simulator.pointnet.nest_utils
> highlighting module code... [ 66%] bmtk.simulator.pointnet.pointnetwork
> highlighting module code... [ 67%] bmtk.simulator.pointnet.pointsimulator
> highlighting module code... [ 67%] bmtk.simulator.pointnet.property_map
> highlighting module code... [ 68%] bmtk.simulator.pointnet.sonata_adaptors
> highlighting module code... [ 68%] bmtk.simulator.pointnet.utils
> highlighting module code... [ 69%] bmtk.simulator.popnet.sonata_adaptors
> highlighting module code... [ 69%] bmtk.simulator.popnet.utils
> highlighting module code... [ 70%] bmtk.simulator.utils.simulation_inputs
> highlighting module code... [ 71%] bmtk.simulator.utils.simulation_reports
> highlighting module code... [ 71%] bmtk.tests.simulator.bionet.bionet_virtual_files
> highlighting module code... [ 72%] bmtk.tests.simulator.bionet.set_cell_params
> highlighting module code... [ 72%] bmtk.tests.simulator.bionet.set_syn_params
> highlighting module code... [ 73%] bmtk.tests.simulator.bionet.set_weights
> highlighting module code... [ 73%] bmtk.tests.simulator.bionet.test_biograph
> highlighting module code... [ 74%] bmtk.tests.simulator.bionet.test_gids
> highlighting module code... [ 75%] bmtk.tests.simulator.bionet.test_nrn
> highlighting module code... [ 75%] bmtk.tests.simulator.bionet.test_virtualcell
> highlighting module code... [ 76%] bmtk.tests.simulator.pointnet.conftest
> highlighting module code... [ 76%] bmtk.tests.simulator.pointnet.pointnet_virtual_files
> highlighting module code... [ 77%] bmtk.tests.simulator.pointnet.test_glif_utils
> highlighting module code... [ 78%] bmtk.tests.simulator.pointnet.test_multimeter_report
> highlighting module code... [ 78%] bmtk.tests.simulator.pointnet.test_pointgraph
> highlighting module code... [ 79%] bmtk.tests.simulator.pointnet.test_pointnetwork
> highlighting module code... [ 79%] bmtk.tests.simulator.popnet.popnet_virtual_files
> highlighting module code... [ 80%] bmtk.tests.simulator.popnet.test_popgraph
> highlighting module code... [ 80%] bmtk.utils.compile_mechanisms.compile_mechanisms
> highlighting module code... [ 81%] bmtk.utils.create_environment.create_environment
> highlighting module code... [ 82%] bmtk.utils.create_environment.env_builder
> highlighting module code... [ 82%] bmtk.utils.hdf5_helper
> highlighting module code... [ 83%] bmtk.utils.io
> highlighting module code... [ 83%] bmtk.utils.io.cell_vars
> highlighting module code... [ 84%] bmtk.utils.io.firing_rates
> highlighting module code... [ 84%] bmtk.utils.io.ioutils
> highlighting module code... [ 85%] bmtk.utils.io.spike_trains
> highlighting module code... [ 86%] bmtk.utils.reports.compartment.compartment_reader
> highlighting module code... [ 86%] bmtk.utils.reports.compartment.compartment_report
> highlighting module code... [ 87%] bmtk.utils.reports.compartment.compartment_writer
> highlighting module code... [ 87%] bmtk.utils.reports.compartment.core
> highlighting module code... [ 88%] bmtk.utils.reports.compartment.plotting
> highlighting module code... [ 89%] bmtk.utils.reports.current_writer
> highlighting module code... [ 89%] bmtk.utils.reports.spike_trains.core
> highlighting module code... [ 90%] bmtk.utils.reports.spike_trains.plotting
> highlighting module code... [ 90%] bmtk.utils.reports.spike_trains.spike_train_buffer
> highlighting module code... [ 91%] bmtk.utils.reports.spike_trains.spike_train_readers
> highlighting module code... [ 91%] bmtk.utils.reports.spike_trains.spike_trains
> highlighting module code... [ 92%] bmtk.utils.reports.spike_trains.spike_trains_api
> highlighting module code... [ 93%] bmtk.utils.reports.spike_trains.spikes_file_writers
> highlighting module code... [ 93%] bmtk.utils.reports.spike_trains.stats
> highlighting module code... [ 94%] bmtk.utils.sim_setup
> highlighting module code... [ 94%] bmtk.utils.sonata.column_property
> highlighting module code... [ 95%] bmtk.utils.sonata.config.sonata_config
> highlighting module code... [ 95%] bmtk.utils.sonata.edge
> highlighting module code... [ 96%] bmtk.utils.sonata.file
> highlighting module code... [ 97%] bmtk.utils.sonata.file_root
> highlighting module code... [ 97%] bmtk.utils.sonata.group
> highlighting module code... [ 98%] bmtk.utils.sonata.node
> highlighting module code... [ 98%] bmtk.utils.sonata.population
> highlighting module code... [ 99%] bmtk.utils.sonata.types_table
> highlighting module code... [100%] bmtk.utils.sonata.utils
> 
> writing additional pages... search done
> copying images... [  1%] _static/images/bmtk_architecture_analyzer_highlight.jpg
> copying images... [  3%] _static/images/spikes_report.png
> copying images... [  5%] _static/images/cell_reports.png
> copying images... [  7%] _static/images/segmentation_indexing.jpg
> copying images... [  9%] _static/images/bmtk_architecture_bionet_highlight.jpg
> copying images... [ 10%] _static/images/disconnected_normal_sims.png
> copying images... [ 12%] _static/images/disconnected_recurrent_only.png
> copying images... [ 14%] _static/images/disconnected_scnn1a.png
> copying images... [ 16%] _static/images/all_network_cropped.png
> copying images... [ 18%] _static/images/ext_inputs_raster.png
> copying images... [ 20%] _static/images/v1_raster.png
> copying images... [ 21%] _static/images/bmtk_architecture_builder_highlight.jpg
> copying images... [ 23%] _static/images/builder_add_nodes.jpg
> copying images... [ 25%] _static/images/builder_add_edges.jpg
> copying images... [ 27%] _static/images/builder_complete_network.jpg
> copying images... [ 29%] _static/images/sonata_structure.jpg
> copying images... [ 30%] _static/images/bmtk_architecture_filternet_highlight.jpg
> copying images... [ 32%] _static/images/lnp_model.jpg
> copying images... [ 34%] _static/images/levels_of_resolution_noml.png
> copying images... [ 36%] _static/images/bmtk_workflow.jpg
> copying images... [ 38%] _static/images/bmtk_architecture.jpg
> copying images... [ 40%] _static/images/graph_structure.png
> copying images... [ 41%] _static/images/nodes_h5_structure.png
> copying images... [ 43%] _static/images/node_types.png
> copying images... [ 45%] _static/images/edges_h5_structure.png
> copying images... [ 47%] _static/images/edge_types.png
> copying images... [ 49%] _static/images/bmtk_architecture_pointnet_highlight.jpg
> copying images... [ 50%] _static/images/bmtk_architecture_popnet_highlight.jpg
> copying images... [ 52%] _static/images/bmtk_architecture_simulator_highlight.jpg
> copying images... [ 54%] _static/images/brunel_comparisons.jpg
> copying images... [ 56%] _static/images/bmtk_sim_env.png
> copying images... [ 58%] _static/_tutorial_images/bmtk_lnp.png
> copying images... [ 60%] ../../../build/html/.doctrees/nbsphinx/tutorial_filter_models_9_0.png
> copying images... [ 61%] _static/_tutorial_images/filternet_spat_filter.png
> copying images... [ 63%] _static/_tutorial_images/filternet_temp_filter.png
> copying images... [ 65%] _static/_tutorial_images/filternet_sfilt_params.png
> copying images... [ 67%] _static/_tutorial_images/filternet_tfilt_params.png
> copying images... [ 69%] ../../../build/html/.doctrees/nbsphinx/tutorial_multi_pop_26_0.png
> copying images... [ 70%] ../../../build/html/.doctrees/nbsphinx/tutorial_multi_pop_26_1.png
> copying images... [ 72%] ../../../build/html/.doctrees/nbsphinx/tutorial_multi_pop_28_0.png
> copying images... [ 74%] ../../../build/html/.doctrees/nbsphinx/tutorial_multi_pop_28_1.png
> copying images... [ 76%] ../../../build/html/.doctrees/nbsphinx/tutorial_multi_pop_30_0.png
> copying images... [ 78%] ../../../build/html/.doctrees/nbsphinx/tutorial_pointnet_modeling_27_0.png
> copying images... [ 80%] ../../../build/html/.doctrees/nbsphinx/tutorial_pointnet_modeling_29_0.png
> copying images... [ 81%] ../../../build/html/.doctrees/nbsphinx/tutorial_pointnet_modeling_33_0.png
> copying images... [ 83%] _static/_tutorial_images/raster_120cells_orig.png
> copying images... [ 85%] _static/_tutorial_images/raster_120cells_perturbed.png
> copying images... [ 87%] ../../../build/html/.doctrees/nbsphinx/tutorial_population_modeling_18_0.png
> copying images... [ 89%] ../../../build/html/.doctrees/nbsphinx/tutorial_single_cell_clamped_16_0.png
> copying images... [ 90%] ../../../build/html/.doctrees/nbsphinx/tutorial_single_cell_clamped_16_1.png
> copying images... [ 92%] ../../../build/html/.doctrees/nbsphinx/tutorial_single_cell_syn_22_0.png
> copying images... [ 94%] ../../../build/html/.doctrees/nbsphinx/tutorial_single_cell_syn_22_1.png
> copying images... [ 96%] ../../../build/html/.doctrees/nbsphinx/tutorial_single_pop_19_0.png
> copying images... [ 98%] ../../../build/html/.doctrees/nbsphinx/tutorial_single_pop_21_0.png
> copying images... [100%] ../../../build/html/.doctrees/nbsphinx/tutorial_single_pop_21_1.png
> 
> copying static files... done
> copying extra files... done
> dumping search index in English (code: en)... done
> dumping object inventory... done
> build succeeded, 100 warnings.
> 
> The HTML pages are in build/html.
> make[1]: Leaving directory '/<<PKGBUILDDIR>>'
>    dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:291: cd /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build; python3.11 -m pytest /<<PKGBUILDDIR>>/bmtk/tests/
> Warning: no DISPLAY environment variable.
> --No graphics will be displayed.
> ============================= test session starts ==============================
> platform linux -- Python 3.11.4, pytest-7.4.0, pluggy-1.2.0
> rootdir: /<<PKGBUILDDIR>>
> collected 276 items / 9 errors / 1 skipped
> 
> ==================================== ERRORS ====================================
> ________ ERROR collecting bmtk/tests/simulator/bionet/test_biograph.py _________
> ImportError while importing test module '/<<PKGBUILDDIR>>/bmtk/tests/simulator/bionet/test_biograph.py'.
> Hint: make sure your test modules/packages have valid Python names.
> Traceback:
> /usr/lib/python3.11/importlib/__init__.py:126: in import_module
>     return _bootstrap._gcd_import(name[level:], package, level)
> ../../../bmtk/tests/simulator/bionet/test_biograph.py:5: in <module>
>     from .conftest import *
> E   ImportError: attempted relative import with no known parent package
> __________ ERROR collecting bmtk/tests/simulator/bionet/test_gids.py ___________
> ImportError while importing test module '/<<PKGBUILDDIR>>/bmtk/tests/simulator/bionet/test_gids.py'.
> Hint: make sure your test modules/packages have valid Python names.
> Traceback:
> /usr/lib/python3.11/importlib/__init__.py:126: in import_module
>     return _bootstrap._gcd_import(name[level:], package, level)
> ../../../bmtk/tests/simulator/bionet/test_gids.py:2: in <module>
>     from .conftest import *
> E   ImportError: attempted relative import with no known parent package
> ___________ ERROR collecting bmtk/tests/simulator/bionet/test_nrn.py ___________
> ImportError while importing test module '/<<PKGBUILDDIR>>/bmtk/tests/simulator/bionet/test_nrn.py'.
> Hint: make sure your test modules/packages have valid Python names.
> Traceback:
> /usr/lib/python3.11/importlib/__init__.py:126: in import_module
>     return _bootstrap._gcd_import(name[level:], package, level)
> ../../../bmtk/tests/simulator/bionet/test_nrn.py:2: in <module>
>     from .conftest import *
> E   ImportError: attempted relative import with no known parent package
> _______ ERROR collecting bmtk/tests/simulator/bionet/test_virtualcell.py _______
> ImportError while importing test module '/<<PKGBUILDDIR>>/bmtk/tests/simulator/bionet/test_virtualcell.py'.
> Hint: make sure your test modules/packages have valid Python names.
> Traceback:
> /usr/lib/python3.11/importlib/__init__.py:126: in import_module
>     return _bootstrap._gcd_import(name[level:], package, level)
> ../../../bmtk/tests/simulator/bionet/test_virtualcell.py:3: in <module>
>     from .conftest import *
> E   ImportError: attempted relative import with no known parent package
> ___ ERROR collecting bmtk/tests/simulator/pointnet/test_multimeter_report.py ___
> ImportError while importing test module '/<<PKGBUILDDIR>>/bmtk/tests/simulator/pointnet/test_multimeter_report.py'.
> Hint: make sure your test modules/packages have valid Python names.
> Traceback:
> /usr/lib/python3.11/importlib/__init__.py:126: in import_module
>     return _bootstrap._gcd_import(name[level:], package, level)
> ../../../bmtk/tests/simulator/pointnet/test_multimeter_report.py:2: in <module>
>     from .conftest import *
> E   ImportError: attempted relative import with no known parent package
> ______ ERROR collecting bmtk/tests/simulator/pointnet/test_pointgraph.py _______
> ImportError while importing test module '/<<PKGBUILDDIR>>/bmtk/tests/simulator/pointnet/test_pointgraph.py'.
> Hint: make sure your test modules/packages have valid Python names.
> Traceback:
> /usr/lib/python3.11/importlib/__init__.py:126: in import_module
>     return _bootstrap._gcd_import(name[level:], package, level)
> ../../../bmtk/tests/simulator/pointnet/test_pointgraph.py:6: in <module>
>     from .conftest import *
> E   ImportError: attempted relative import with no known parent package
> _____ ERROR collecting bmtk/tests/simulator/pointnet/test_pointnetwork.py ______
> ImportError while importing test module '/<<PKGBUILDDIR>>/bmtk/tests/simulator/pointnet/test_pointnetwork.py'.
> Hint: make sure your test modules/packages have valid Python names.
> Traceback:
> /usr/lib/python3.11/importlib/__init__.py:126: in import_module
>     return _bootstrap._gcd_import(name[level:], package, level)
> ../../../bmtk/tests/simulator/pointnet/test_pointnetwork.py:3: in <module>
>     from .conftest import *
> E   ImportError: attempted relative import with no known parent package
> ________ ERROR collecting bmtk/tests/simulator/popnet/test_popgraph.py _________
> ImportError while importing test module '/<<PKGBUILDDIR>>/bmtk/tests/simulator/popnet/test_popgraph.py'.
> Hint: make sure your test modules/packages have valid Python names.
> Traceback:
> /usr/lib/python3.11/importlib/__init__.py:126: in import_module
>     return _bootstrap._gcd_import(name[level:], package, level)
> ../../../bmtk/tests/simulator/popnet/test_popgraph.py:5: in <module>
>     from . import popnet_virtual_files as pvf
> E   ImportError: attempted relative import with no known parent package
> ___ ERROR collecting bmtk/tests/utils/reports/spike_trains/test_plotting.py ____
> import file mismatch:
> imported module 'test_plotting' has this __file__ attribute:
>   /<<PKGBUILDDIR>>/bmtk/tests/utils/reports/compartment/test_plotting.py
> which is not the same as the test file we want to collect:
>   /<<PKGBUILDDIR>>/bmtk/tests/utils/reports/spike_trains/test_plotting.py
> HINT: remove __pycache__ / .pyc files and/or use a unique basename for your test file modules
> =============================== warnings summary ===============================
> bmtk/utils/sonata/config/sonata_config.py:400
>   /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/utils/sonata/config/sonata_config.py:400: DeprecationWarning: invalid escape sequence '\$'
>     variables = [m for m in re.finditer('\$\{?[\w]+\}?', json_str)]
> 
> bmtk/simulator/filternet/lgnmodel/util_fns.py:51
>   /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/bmtk/simulator/filternet/lgnmodel/util_fns.py:51: DeprecationWarning: invalid escape sequence '\D'
>     gr_fnames_ord = sorted(gr_fnames, key=lambda x: (int(re.sub('\D', '', x)), x))
> 
> -- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html
> =========================== short test summary info ============================
> ERROR ../../../bmtk/tests/simulator/bionet/test_biograph.py
> ERROR ../../../bmtk/tests/simulator/bionet/test_gids.py
> ERROR ../../../bmtk/tests/simulator/bionet/test_nrn.py
> ERROR ../../../bmtk/tests/simulator/bionet/test_virtualcell.py
> ERROR ../../../bmtk/tests/simulator/pointnet/test_multimeter_report.py
> ERROR ../../../bmtk/tests/simulator/pointnet/test_pointgraph.py
> ERROR ../../../bmtk/tests/simulator/pointnet/test_pointnetwork.py
> ERROR ../../../bmtk/tests/simulator/popnet/test_popgraph.py
> ERROR ../../../bmtk/tests/utils/reports/spike_trains/test_plotting.py
> !!!!!!!!!!!!!!!!!!! Interrupted: 9 errors during collection !!!!!!!!!!!!!!!!!!!!
> =================== 1 skipped, 2 warnings, 9 errors in 5.41s ===================
> E: pybuild pybuild:395: test: plugin distutils failed with: exit code=2: cd /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build; python3.11 -m pytest {dir}/bmtk/tests/
> dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13
> make: *** [debian/rules:13: binary] Error 25
> dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
> 
> E: Command 'cd /<<PKGBUILDDIR>> && runuser -u user42 -- dpkg-buildpackage --sanitize-env -us -uc -rfakeroot -b' failed to run.


The full build log is available from:
http://qa-logs.debian.net/2023/08/16/bmtk_1.0.6+ds-1_unstable.log

If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.