[Question] Can Env.render take arguments?

[qgallouedec]

Question

This line suggests that it is possible to pass [keyword] arguments to the gym.Env.render method.

Gymnasium/gymnasium/wrappers/pixel_observation.py

Line 199 in b4caf9d

render = self.env.render(*args, **kwargs)

Which seems not to be consistent with how gym.Env is implemented in core.

Gymnasium/gymnasium/core.py

Line 146 in d46ff0e

def render(self) -> RenderFrame | list[RenderFrame] | None:

Am I right?

[RedTachyon]

It used to be the case that env.render() would take arguments, but we changed it a few releases ago. Now you set it with env = gym.make(..., render_mode="rgb_array"), and call env.render() without any arguments. The code you mentioned hasn't been properly updated since, although technically speaking I guess it doesn't really break anything.

[qgallouedec]

Thanks for the clarification. Then the render_kwargs arg in the constructor is inoperative right?

[qgallouedec]

I've just seen #301 (comment). Should we consider PixelObservationWrapper as deprecated then? I read in your roadmap #12 "Release v0.29.0 as an intermediate version with experimental functional, new wrappers and vectors to root". Does it mean that PixelObservationWrapper is going to be replaced by experimental.wrappers.PixelObservationv0 in 0.29?

[pseudo-rnd-thoughts]

The roadmap needs to be updated for a new release in the next week not listed on the roadmap so it will replace PixelObservationWrapper in v0.31