For now, only allow brian units for preferences (don't import numpy and
scipy -- this clashes with doc generation where we mock scipy)
Finished outline documentation of code generation system
Merge branch 'master' of https://github.com/brian-team/brian2.git
Actually we *do* need numpy in the preferences, at least to specify datatypes (e.g. float64).
Refactored brian2.codegen.parsing into brian2.codegen.sympytools and
brian2.parsing.statements
Assorted documentation fixes
Use pure numpy arrays instead of dimensionless Quantity objects when possible
Implement new indexing semantic for StateMonitor, closes #88
Add tests for the new indexing semantics
Replace numpy scalar values with numpy data types with their Python equivalents (e.g. replace np.int64(1) with int(1)) -- weave otherwise treats them as general Python objects, not as numbers
Replace numpy scalar values with numpy data types with their Python equivalents (e.g. replace np.int64(1) with int(1)) -- weave otherwise treats them as general Python objects, not as numbers
Merge pull request #90 from brian-team/monitor_return_values

Implement indexing semantics for StateMonitor
Merge remote-tracking branch 'origin/master' into specifiers_rewrite

Conflicts:
	brian2/equations/unitcheck.py
	brian2/monitors/statemonitor.py
	brian2/stateupdaters/exact.py
	docs_sphinx/developer/codegen.rst