Open j-i-l opened 3 months ago
The convention is (scipy is actually a terrible example for this):
scipy
snake_case
PascalCase
so:
SparseStochMat.py -> sparse_stoch_mat.py class sparse_stoch_mat -> class SparseStochMat (I'd even go for just SSM)
class sparse_stoch_mat
class SparseStochMat
SSM
There are other namings that we might want to change:
SynthTempNetwork.py
synth_temp_network.py
And some we might want to keep (like Upper_case names for matrix-like objects).
Upper_case
@alexbovet should we go for that or keep the current naming scheme?
Yes, let's follow the convention (but keep SparseStochMat, not SSM, and keep upper case for matrices).
The convention is (
scipy
is actually a terrible example for this):snake_case
for module namesPascalCase
for class namesso:
SparseStochMat.py -> sparse_stoch_mat.py
class sparse_stoch_mat
->class SparseStochMat
(I'd even go for justSSM
)There are other namings that we might want to change:
SynthTempNetwork.py
>synth_temp_network.py
And some we might want to keep (like
Upper_case
names for matrix-like objects).