You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
but are still respected, when the newly named parameters are not set. Deprecation warnings are issued if they are still used.
For context, see also #323.
We still need to decide when to finally remove them: Maybe at a fixed date or in terms of number of releases?
The text was updated successfully, but these errors were encountered:
Thanks @jolange for opening this issue, and thanks again for all you work!
As you've probably seen, release are not quite regular here... So a number of releases could take years.
What I propose is to make a new major release of dask-jobqueue soon (in the coming days or week), version 0.8.0, as a good number of changes has been commited. Then we could agree on a maximum delay before removing the old parameters. What about 6 months? Or maybe one year?
We could say we need to remove the old parameters and deprecation message either after 6 months, either if we plan a new major release until then?
I propose is to make a new major release of dask-jobqueue soon (in the coming days or week), version 0.8.0
Sounds good.
What about 6 months? Or maybe one year?
6 months sounds enough to me, personally. Of course, given that the deprecation warning has been included in a published release for some time, which should be the case with your plans for a new release.
The parameters have been renamed in
env_extra
#575extra
#576job_extra
#577but are still respected, when the newly named parameters are not set. Deprecation warnings are issued if they are still used.
For context, see also #323.
We still need to decide when to finally remove them: Maybe at a fixed date or in terms of number of releases?
The text was updated successfully, but these errors were encountered: