Closed pramodak closed 1 year ago
This has been possibly fixed with some of the "revival" updates (merged to master with 5e0dccc604c454ece1b6c0e794733fcec69d892a).
I can now successfully run:
user@machine:~/JNC/examples/0-intro$ python3 --version
Python 3.8.10
user@machine:~/JNC/examples/0-intro$ pyang --version
pyang 2.5.3
user@machine:~/JNC/examples/0-intro$ head -3 `which pyang`
#!/usr/bin/python3
user@machine:~/JNC/examples/0-intro$
user@machine:~/JNC/examples/0-intro$ pyang -f jnc --jnc-no-pkginfo --jnc-output out/src ./hosts.yang --path ~/confd/confd-7.4/src/confd/yang/
user@machine:~/JNC/examples/0-intro$ tree out/ | head -8
out/
└── src
├── hosts
│ ├── Conny.java
│ ├── Hosts.java
│ ├── Rej.java
│ ├── Simple.java
│ ├── Simple.schema
We are moving to python3 (since python2 is deprecated) and we see an issue while generating java classes with the below command (which was working with python2 + pyang 2.5.2)
/tmp/pyang-2.5.2/bin/pyang -f jnc --jnc-no-pkginfo --jnc-output /tmp/out/ <yang>
Stack trace:
If there is a workaround could anyone help? Do we have to define the __hash__() method for JavaMethod class of jnc module? - Is there any reference?