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

Use long type for GEXF with Python2 long or Python3 int. #941

Merged
merged 1 commit into from
Aug 27, 2013

Conversation

hagberg
Copy link
Member

@hagberg hagberg commented Aug 24, 2013

GEXF has a "long" integer type. Use that for Python2 longs and the standard Python3 int.

Addresses #940

hagberg added a commit that referenced this pull request Aug 27, 2013
Use long type for GEXF with Python2 long or Python3 int.

Fixes #940
@hagberg hagberg merged commit 63a345d into networkx:master Aug 27, 2013
@hagberg hagberg deleted the gexf-long branch August 27, 2013 23:18
@gdbassett
Copy link

A few days after making the changes I have had some issues with properties showing up as lists when they were really strings or longs. I have no clue if this is related to this issue but it would be worth keeping an eye on.

EDIT: I reverted the changes and ran and am still having the issues. IT may be an issue with gephi's import script.

@hagberg
Copy link
Member Author

hagberg commented Aug 30, 2013

Could you be more specific about this issue? Maybe an example?

On Fri, Aug 30, 2013 at 7:07 AM, Gabe notifications@github.com wrote:

A few days after making the changes I have had some issues with properties
showing up as lists when they were really strings or longs. I have no clue
if this is related to this issue but it would be worth keeping an eye on.


Reply to this email directly or view it on GitHubhttps://github.com//pull/941#issuecomment-23559604
.

@gdbassett
Copy link

I don't think it was networkx. I think gephi noticed a time in the attributes and started acting weird. The .gexf it's self looks fine.

@hagberg hagberg added this to the networkx-1.9 milestone May 13, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants