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

ip_ext_full produces inconsistent results #23

Closed
GoogleCodeExporter opened this issue Mar 18, 2015 · 2 comments
Closed

ip_ext_full produces inconsistent results #23

GoogleCodeExporter opened this issue Mar 18, 2015 · 2 comments

Comments

@GoogleCodeExporter
Copy link

What steps will reproduce the problem?

1. Use ip_ext_full for valid addr without double ':', for ex.

   ipaddr.IPv6('2001:4c30:100:2:2d0:b7ff:fed3:9a').ip_ext_full

We get:
2001:4c30:100:2:2d0:b7ff:fed3:9a 
but IMVHO it should be:
2001:4c30:0100:0002:02d0:b7ff:fed3:009a 
- like result for addr 2001:658:22A:CAFE:200::1.

What version of the product are you using? On what operating system?

ipaddr-py from trunk, python2.5 on Ubuntu 8.04

Please provide any additional information below.

Fix is simple, small patch for _explode_shorthand_ip_string in attachement.

Original issue reported on code.google.com by an...@smutek.pl on 19 Jun 2009 at 7:24

Attachments:

@GoogleCodeExporter
Copy link
Author

Patch is also available at http://codereview.appspot.com/79053

Original comment by an...@smutek.pl on 19 Jun 2009 at 7:28

@GoogleCodeExporter
Copy link
Author

sorry for the delay in acting on this.

fixed for the 1.1.x branch in r100. I'm not sure if this is still an issue, but 
checkout the 2.0 branch.  now to double check that explode works properly in 
2.0 :)

Original comment by pmo...@google.com on 30 Aug 2009 at 12:36

  • Changed state: Fixed

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