This is what it might look like to implement https://github.com/dagster-io/dagster/discussions/3132
I do think this is an interesting case where overdoing it on "progressive disclosure of complexity" actually did active damage. The original idea was to be able to delay the introduction of the context object, at the expense of having an increase API surface. In this case it is pretty clear that that tradeoff was incorrect
let's just change the warning to say it is being deleted. i doubt it is very broadly used.
Here's another idea. At 0.10.0 we could change it to
def lambda_solid(*args, **args): raise ApiDeletedException('Some text about using @solid instead')
That is *a lot* more informative than an import error. Now that I think about this would be an interesting generalized pattern for renames