nats-py to nats-core migration.

[farzbood]

Hi Community,
Since the initial-release of nats-core (the new performant NATS python client library) I'm wondered if it's a drop-in replacement, or there's a migration guideline from nats-py to nats-core ?
Happy Messaging ⚡

[ff137]

Would be great to get some feedback on this. Couldn't help but notice there's a new nats-core release, but no mention of it in the README, and no real user guide or info on what's different, and how to use it.

I tested it out, and because the package structure is a lil different, it's not a drop-in replacement. The init files can be expanded to include more imports for migration compatibility. But then again, JetStream is not available in nats-core, so it doesn't seem possible for JS users to switch from nats-py to nats-core.

Some feedback about usage / migration, and maybe a "roadmap" for nats-core, will be much appreciated! Then others in the community can help build towards what's needed.

cc: @wallyqs @caspervonb

[ff137]

PS: Seems like this PR has the other round of jetstream changes: #734

[Jarema]

This is a new early-verison release, that's why there is yet no oficial migration guide.

The idea behind is to have a much more performant, idiomatic Python nats client.
It is mostly feature completre, but it is a preview.

We will soon drop readme with details about it.