Remove remaining references to weave

Author: mstimberg

brian2/codegen/runtime/cython_rt/templates/group_variable_get_conditional.pyx

@@ -4,7 +4,6 @@
 
 {% block maincode %}
 
-    {# This is copied from the weave equivalent, seems to work but confusing #}
     {%set c_type = cpp_dtype(variables['_variable'].dtype) %}
     {%set np_type = numpy_dtype(variables['_variable'].dtype) %}
 

brian2/core/preferences.py

@@ -31,8 +31,8 @@ def parse_preference_name(name):
     
     Examples
     --------
-    >>> parse_preference_name('core.weave_compiler')
-    ('core', 'weave_compiler')
+    >>> parse_preference_name('core.default_float_dtype')
+    ('core', 'default_float_dtype')
     >>> parse_preference_name('codegen.cpp.compiler')
     ('codegen.cpp', 'compiler')
     '''

docs_sphinx/developer/GSL.rst

@@ -73,10 +73,10 @@ Return value of the StateUpdateMethod
 So far, for each each code generation language (numpy, cython) there was just
 one set of rules of how to translate abstract code to real code, described in
 its respective `CodeObject` and `CodeGenerator`. If the target language is set
-to weave, the stateupdater will use the `WeaveCodeObject`, just like other
+to Cython, the stateupdater will use the `CythonCodeObject`, just like other
 objects such as the `StateMonitor`. However, to achieve the above decribed
 translations of the abstract code generated by the `StateUpdateMethod`, we
-need a special `WeaveCodeObject` for the stateupdater alone (which at its turn
+need a special `CythonCodeObject` for the stateupdater alone (which at its turn
 can contain the special `CodeGenerator`), and this `CodeObject` should be
 selected based on the chosen `StateUpdateMethod`.
 

docs_sphinx/developer/functions.rst

@@ -12,7 +12,7 @@ To add a new implementation for a code generation target, a
 `FunctionImplementation` can be added to the `Function.implementations`
 dictionary. The key for this dictionary has to be either a `CodeGenerator` class
 object, or a `CodeObject` class object. The `CodeGenerator` of a `CodeObject`
-(e.g. `CPPCodeGenerator` for `WeaveCodeObject`) is used as a fallback if no
+(e.g. `CPPCodeGenerator` for `CPPStandaloneCodeObject`) is used as a fallback if no
 implementation specific to the `CodeObject` class exists.
 
 If a function is already provided for the target language (e.g. it is part of

docs_sphinx/introduction/brian1_to_2/preferences.rst

@@ -40,7 +40,8 @@ Preference name changes
 
 * ``defaultclock``: removed because it led to unclear behaviour of scripts.
 * ``useweave_linear_diffeq``: removed because it was no longer relevant.
-* ``useweave``: now replaced by `codegen.target`.
+* ``useweave``: now replaced by `codegen.target` (but note that weave is no longer
+  supported in Brian 2, use Cython instead).
 * ``weavecompiler``: now replaced by `codegen.cpp.compiler`.
 * ``gcc_options``: now replaced by `codegen.cpp.extra_compile_args_gcc`.
 * ``openmp``: now replaced by `devices.cpp_standalone.openmp_threads`.