ecmwfr
ecmwfr copied to clipboard
Restores request$request_id functionality
Closes #99
Any idea why macOS is failing?
Perhaps we need to document the redundancy and prepare a deprecation pathway for future releases?
Yes, but I would not jump the gun. The fact that this triggered 2 issues indicates to me that people have used this workflow, in part to get around some of the constraints. Now, these have been lifted by your implementation but I hate to break code if not necessary. Now, obviously, this further entrenches a stale usage pattern. A bit of a catch 22.
So I think the best we can do toward the future is give some sort of warning when called (with strong pointers to how things are done now), and keep this alive for a couple of cycles. Sadly there is no real way to contact users, other than some noise on twitter. :(
Yes, adding warnings for a couple of releases and such should be enough.