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

phyport split causes import failure #86

Closed
supertylerc opened this Issue Jan 22, 2014 · 3 comments

Comments

Projects
None yet
2 participants
@supertylerc
Copy link

supertylerc commented Jan 22, 2014

The error below is generated on an Ubuntu 12.04 system after running the installation instructions from README.md.

>>> from jnpr.junos.op.phyport import *
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/usr/local/lib/python2.7/dist-packages/junos_eznc-0.0.2-py2.7.egg/jnpr/junos/op/phyport.py", line 3, in <module>
    globals().update(loadyaml(_yml_file))
  File "/usr/local/lib/python2.7/dist-packages/junos_eznc-0.0.2-py2.7.egg/jnpr/junos/factory/loadyaml.py", line 33, in loadyaml
    return FactoryLoader().load( yaml.load( open(path, 'r' )))
IOError: [Errno 2] No such file or directory: '/usr/local/lib/python2.yml'

I found that editing /usr/local/lib/python2.7/dist-packages/junos_eznc-0.0.2-py2.7.egg/jnpr/junos/op/phyport.py and making the changes suggested in #62 resolved the issue.

@jeremyschulman

This comment has been minimized.

Copy link
Member

jeremyschulman commented Jan 22, 2014

@tyler-c - thank you for the post. I see that you are using v0.0.2. I believe this was resolved in v0.0.3. Could you please confirm for your setup?

Thank you!

@supertylerc

This comment has been minimized.

Copy link

supertylerc commented Jan 22, 2014

@jeremyschulman

When was 0.0.3 released? I initially tried with a clone of the repo, but when that failed (with the same error, although perhaps a different cause), I went the pip route. When that failed as well, I started hunting down issues.

Either way, I'll try with 0.0.3 today or tomorrow. Thanks!

@supertylerc

This comment has been minimized.

Copy link

supertylerc commented Jan 23, 2014

@jeremyschulman

Pulling the most recent version of this did resolve the issue. I must have done something incredibly stupid the first time I tried.

Thanks.

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