Remove deprecated features esmvaltool config get_config_user, esmvaltool config get_config_developer, esmvalcore.local.DataSource - #3210
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #3210 +/- ##
==========================================
- Coverage 96.50% 96.45% -0.06%
==========================================
Files 281 281
Lines 16360 16317 -43
==========================================
- Hits 15789 15739 -50
- Misses 571 578 +7 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
bouweandela
left a comment
There was a problem hiding this comment.
Looks good, though esmvalcore.local.DataSource seems a bit unrelated to the command line options that are removed in this pull request, so it may look nicer in the changelog to make it two separate PRs.
|
Yeah, agreed. Originally, I wanted to handle all cases in a single PR, but quickly realized that there are way too many. If you prefer, I can open a separate PR, but we could always manually adapt the changelog (we do this for the backwards-incompatible changes anyway). |
|
Merging this now to allow review of #3211. |
Description
This PRs removes some of the deprecated features that are scheduled for removal in v2.16.0. There are a lot of them, so I thought its best to do this piece by piece.
Backwards-incompatible change #
This PR removes deprecated features that are scheduled for removal in v2.16.0.
esmvaltool config get_config_userDeprecated in #2765. Use
esmvaltool config copyinstead.esmvaltool config get_config_developerThe config-developer.yml file has been deprecated in #2946. The corresponding option are now configured in ESMValCore's configuration. These configuration files can be copied via
esmvaltool config copyinstead.esmvalcore.local.DataSourceDeprecated in #2911. Use
esmvalcore.io.local.LocalDataSourceinstead.Checklist
It is the responsibility of the author to make sure the pull request is ready to review. The icons indicate whether the item will be subject to the 🛠 Technical or 🧪 Scientific review.
🛠 Changes are backward compatibleTo help with the number pull requests: