Import oemof.tabular's base class Facade

[jnnr]

Currently, the facades in oemof.thermal inherit from a base class that has been copied from oemof.tabular. This was done in the beginning to try the concept of facades and reduce the number of imports. Now, as both packages, oemof.tabular and oemof.tabular, get used more and more, we can as well import oemof.tabular. This would help to avoid divergent developments, keep compatibilty and would be in line with the new unbundled repo structure.

[c-moeller]

I would suggest to shift this to v0.0.4 due to the workload in v0.0.3 and current activity in oemof-tabular. Is this ok for you?

[jnnr]

It could be done within a couple of minutes. This is not a lot of work in terms of programming. It may generate some work in the future, if changes have to be coordinated with oemof.tabular. And it will also keep things easier when someone wants to use the two packages together.

It is a decision. if we need some more time for that, there is no need to hurry.

[c-moeller]

Ok, I set it back to v0.0.3

[jnnr]

Currently, importing from oemof.tabular would induce a version conflict:

• oemof.thermal relies on oemof.solph v0.4.0 or higher,
• oemof.tabular is still not updated to oemof.solph v0.4.0.

Therefore, we should not import from oemof.tabular. Once oemof.tabular is updated, we could decide to import from there. I removed the milestone. Shall I leave this issue open as a reminder for later?

[c-moeller]

I would leave it open.