There is a propensity for amazingly long names of methods and variables in this package. Unfortunately, these long names become quite cumbersome to use and difficult to read. Fortunately, good documentation can ameliorate the issue. While these isn't an exact rule for name length (e.g., in PEP8),
That being said, is there any opposition to renaming methods that are over ~70 characters long? This will at least give room for two 4-space indents + a trailing parenthesis.
There is a propensity for amazingly long names of methods and variables in this package. Unfortunately, these long names become quite cumbersome to use and difficult to read. Fortunately, good documentation can ameliorate the issue. While these isn't an exact rule for name length (e.g., in PEP8),
That being said, is there any opposition to renaming methods that are over ~70 characters long? This will at least give room for two 4-space indents + a trailing parenthesis.
So far, I found these culprits:
egrid_facilities.list_facilities_w_percent_generation_from_primary_fuel_category_greater_than_min
(so long!)egrid_filter.egrid_facilities_w_percent_generation_from_primary_fuel_category_greater_than_min
(such a long variable name!)generation_mix.create_generation_mix_process_df_from_model_generation_data
(so long!)generation_mix.ref_egrid_subregion_generation_by_fuelcategory_with_NERC