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

deprecate multiValue mode for mapping.Mapping #107

Open
GoogleCodeExporter opened this issue Apr 8, 2016 · 0 comments
Open

deprecate multiValue mode for mapping.Mapping #107

GoogleCodeExporter opened this issue Apr 8, 2016 · 0 comments

Comments

@GoogleCodeExporter
Copy link

We should rationalize Pygr's mapping / graph classes.  Specifically,
Mapping should be clearly restricted to one:one relations; users should use
Graph for *:many relations.  I suggest we deprecate the multiValue option
for Mapping, with a warning message that tells users to use Graph instead.
 For one thing, Mapping's inverse class assumes the original mapping was
one:one.

Original issue reported on code.google.com by cjlee...@gmail.com on 31 Aug 2009 at 9:37

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

No branches or pull requests

1 participant