Einar Nilsen-Nygaard

@jalphonso, `ncclient` is maintained by volunteers, so, if you are able and willing to consider contributing via code, then that would be great! For now, I will mark this as...

@earies, are you considering bringing this PR up to date with the current main line?

@Alessandro-Barbieri, could you take a look at the changes on the branch `einarnn-pep517` and see if they deliver what you're after: https://github.com/ncclient/ncclient/tree/einarnn-pep517 Thanks!

I always package ncclient in an isolated environment to avoid clashes. I have attached a source tar.gz file you can try installing if you like. I am not an expert...

Or this one: [ncclient-0.6.13+6.g2413a91.tar.gz](https://github.com/ncclient/ncclient/files/8747353/ncclient-0.6.13%2B6.g2413a91.tar.gz)

@Alessandro-Barbieri, the changes I have made seem to work in a fairly standard environment, and the `pyproject.toml` file I have added is consulted in my standard environment using pip. However,...

@elliotCooper, beginning of an enhancement in #543.

@lavanyasingaravelanT, if your config is particularly large, `huge_tree=True` will still result in memory exhaustion.

@lavanyasingaravelanT, have you tried using the custom RPC from the JunOS device extension to get configuration for JunOS platforms? I'm not sure if that will help...?

No direct issue with ncclient. For dealing with really large we may benefit from a streaming interface to retrieve data. However, this would necessitate substantial refactoring. So marking this issue...