Remove Configobj as Dependency Due To Security Vulnerability and No Longer Maintaned

[aarande]

Remove Configobj as Dependency Due To Security Vulnerability and No Longer Maintaned

[djhoese]

Configobj is used for parsing all legacy format areas config files. The newer format uses YAML. It would be a major deprecation to remove support for the legacy format. That said, no new uses of pyresample should be using this older format (we don't use it in Satpy for example). Dropping support for the configobj format was my plan as part of pyresample 2.0, but I'm not sure what the timeline is for that release given my funding for that type of development has dried up. I'd be OK removing it as a hard requirement with plenty of deprecation warnings added.

@mraspaud @pnuu and others, what are your thoughts?

[pnuu]

I would be fine removing the legacy area definition support. I think we've had the yaml version already for so long, that even without a deprecation cycle it should be pretty safe. If someone is still using them, I doubt they'd notice the deprecation messages anyway 😅

[djhoese]

If someone is still using them, I doubt they'd notice the deprecation messages anyway

This is a good point. We could have a release or two with it non-functional or with the hard requirement removed. Then in 2.0 or maybe sooner we could remove the functionality entirely.