docs(nx-python): update README

[busla]

Update README with example

I think this plugin has a lot of potential given that developing non-js plugins is a complex task, well done 💪🏼

I thought I'd start adding a PR with configuration examples but perhaps it's better to just add a single example for now and get feedback on how (and if) you would like a chapter per target with json config examples.

I can then add some more.

[busla]

I am noticing that package-lock.json was modified, that is weird 🤷🏼

Perhaps pinning node and npm versions in package.json might help.

Here is my env:

# nx --version
Nx Version:
- Local: v16.3.2
- Global: Not found

# npm --version
9.6.7

# node --version
v18.17.1

[lucasvieirasilva]

Thanks for contributing to this project, sorry for the delay, could you please revert the changes in this file? since you just changed the readme, I don't think the package-lock.json should be part of this PR.

Thanks!

[lucasvieirasilva]

I am noticing that package-lock.json was modified, that is weird 🤷🏼

Perhaps pinning node and npm versions in package.json might help.

Here is my env:

# nx --version
Nx Version:
- Local: v16.3.2
- Global: Not found

# npm --version
9.6.7

# node --version
v18.17.1

Yep, that's weird, you should use npm ci instead of npm install when you have any intention of adding, changing, or removing any package from the project.

[busla]

I converted the PR to a draft since it's actually an issue. The package-lock got modified by running npm install, which it shouldn't, so I guess it will get modified whenever anyone clones it and runs npm install 🤷.

[lucasvieirasilva]

I guess it will get modified whene

Yes, you're right, let me raise a PR to fix this and I'll let you know.

[lucasvieirasilva]

@busla I've updated the package-lock.json, could you merge the latest changes in the main branch with your branch and see if the package-lock changes are now synced?