Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Should pip install edward>=2.0.0 just use github.com/google/edward2? #937

Open
dustinvtran opened this issue Aug 15, 2019 · 3 comments
Open

Comments

@dustinvtran
Copy link
Member

dustinvtran commented Aug 15, 2019

Discourse post: https://discourse.edwardlib.org/t/should-pip-install-edward-2-0-0-just-use-github-com-google-edward2/1086

We’re setting up a standalone repository for Edward2 (https://github.com/google/edward2). This will let us further develop the excellent examples from Edward1 and community tools like the website and forum. Like Edward1, a high priority is complete transparency, where all discussion will appear publically in pull requests, the issue tracker, and the forum rather than Google’s various internal processes.

Currently, our plans are to use a separate PyPI package edward2. But edward isn’t maintained (it’s broken at latest TF, and certainly not TF 2.0 compatible). Should we just update the PyPI package to edward2 altogether?

@dustinvtran
Copy link
Member Author

dustinvtran commented Aug 15, 2019

@dusenberrymw
@danijar
@markvdw

We may end up moving Bayesian Layers code as well so that we can start building out examples and documentation.

@dusenberrymw
Copy link

I think it’s quite reasonable to use the same PyPI package and mark it as version 2.0. If we choose to do that, we might want to reconsider whether the namespace should be edward2 vs. simply edward.

+1 to moving the Bayesian layers code and building it out.

@dustinvtran
Copy link
Member Author

You're correct. The namespace should be edward if we choose to move.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants