Release 0.7.2

[ClaraBuettner]

I commented all open PR to decide if we want to merge it, close it or keep it open.
Besides, I checked if other newer branches might be merged before this release and added one PR. The other branches are already part of open PR or should be added later (e.g. sclopf).
Looking at the open issues, I think we should

• implement pip dependency links are deprecated #286

• fix the sqlalchemy dependecy problem with eGo (Installation fails due to conflicting sqlalchemy version eGo#155).

I will take a look at these problems and comment here when I found a solution.

In addition, it might be useful to refer to grid dataversion v0.4.6 which can be used only for etrago. I don't know where is the best place for this by now.

[ClaraBuettner]

By implementing the fix in #286, I run into other installation problems which have to be fixed:

• egoio has to be upgraded to v0.4.7 due to installation problems of egoio (see Pip install does not work anymore ego.io#78 and Fix oedialect dependency ego.io#81)
• egoio needs (just like eGo) SQL Alchemy >= 1.2.0, while etrago currently needs SQlAlchemy == 1.1.4
• pypsa v0.11.0 is not compatible to newest versions of pyomo and networkx, so we have to limit the version number. We could either do this in pypsa11fork or in etrago. I think it's easier to add this to etragos setup.py but adding to the pypsa fork would be cleaner. What do you prefer @ulfmueller ?

[ClaraBuettner]

These problems are solved in #291
I decided to change the requirements of pyomo and networkx in etrago to avoid changes n pypsa fork. But I can change this.

[ulfmueller]

A few minor comments:

1. so we do not need the dependency link anymore? Or is it still one - just called differently? If there is none anymore we could/have to change the installation and leave out the "--process-dependency-links" part...
2. I think it is cleaner to do the networkx and pyomo version thing in the pypsa fork. because if our fork does not work with the newer version the setup py there is not functional. I cannot see any problem to specify it in the pypsa fork. do you?

[ulfmueller]

By the way, it would be nice if we could get rid of the fork for the release when we update pypsa. At least we could check if it would be possible by now. just to keep in mind. may be I create an issue for the release after this one...

[ClaraBuettner]

A few minor comments:

1. so we do not need the dependency link anymore? Or is it still one - just called differently? If there is none anymore we could/have to change the installation and leave out the "--process-dependency-links" part...

Yes, we don't need the option --process-dependency-links anymore. There is a link to the fork on github in the requirments: 'pypsa @ git+https://github.com/openego/PyPSA.git@master#egg=pypsa-0.11.0fork'

2. I think it is cleaner to do the networkx and pyomo version thing in the pypsa fork. because if our fork does not work with the newer version the setup py there is not functional. I cannot see any problem to specify it in the pypsa fork. do you?

No there is no problem. I just thought we don't want to change the fork. I can add the requirements to pypsa fork.

[ulfmueller]

Perfect. Can you adjust the installation instructions in that branch too then?

[ClaraBuettner]

I just pushed it to PR #291

[ulfmueller]

I could not see that you changed the installation instructions. I did so now in feature/installation_dependencies. Or did I misunderstand s.th.?

[ClaraBuettner]

You're right, I forgot to change the installation instructions

[ulfmueller]

eTraGo 0.7.2 is released - also on pypi. As a hack for the dependency link to the pypsa fork one has to use the pip version 18.1. This is now also part of the documentation. In future, we will avoid to use the dependency link.