🔧 Make env picklable

[MathisFederico]

Description

I needed envs to be picklable for using them in multiple process.
Thus I fixed the issue that happens to be lambda functions used for missions generation.

Fixes to fact that envs were not picklable.

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)

Checklist:

• I have run the pre-commit checks with pre-commit run --all-files (see CONTRIBUTING.md instructions to set it up)
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation (None?)
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes

[rodrigodelazcano]

Thank you for the PR @MathisFederico. I suggest a few changes. I left a comment for the testing function, and could you update the docs for the MissionSpace class (use static method function instead of lambda function).

[MathisFederico]

I suggest a few changes.

Sure ! Where can I find your suggestions ? I don't think you published your review if you have done one !

could you update the docs for the MissionSpace class

Done in last commit !

[rodrigodelazcano]

Thanks! I just tagged you on it, under tests/test_envs.py

[MathisFederico]

Thanks! I just tagged you on it, under tests/test_envs.py

Not sure where to see the tag ... I guess it's on GitHub as I don't see any new commit from your part, but I can't seem to find where you tagged me ^^'

You may want to use GitHub review system, I've had good experiences with that !

[rodrigodelazcano]

@MathisFederico can you see the review now?

[MathisFederico]

Yes ! Sorry I did not have time for now, I may do this tonight if I can find the time !

[MathisFederico]

Done ! @rodrigodelazcano