Update Readme

[KrishnaTO]

Fixed typo from old style git clone url

Encountered error installing in local, using Python v3.12.3, getting 'Externally managed environment' error. Per PEP 668, use of an environment resolves this error.

Alternatively for installing from pip (not from local clone), pipx is required for "External packages" per error.

Please feel free to review and update as needed.

Updated git clone URL matching http method
Added venv-based environment to resolve 'Externally managed environment' error from [PEP 668|https://peps.python.org/pep-0668/] Updated pip installation to pipx, as required for external packages

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Please upload report for BASE (master@1a03dc7). Learn more about missing BASE report.

Additional details and impacted files

@@            Coverage Diff            @@
##             master     #174   +/-   ##
=========================================
  Coverage          ?   28.64%           
=========================================
  Files             ?       16           
  Lines             ?     1351           
  Branches          ?      180           
=========================================
  Hits              ?      387           
  Misses            ?      950           
  Partials          ?       14           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[cthoyt]

Hi @KrishnaTO, thanks for pointing this out, but there are so many ways to make virtual environments that documenting just one specific way how to do this is out of scope for this package's installation documentation.

I'm not sure using a virtual environment is even the root cause for your error - can you please include the full code that you ran in the shell and the full output?

However, the typo fix for git+https is helpful, would you mind making a self-contained contribution with just that?

[KrishnaTO]

Done, but let me know if a separate pull request is better?

[cthoyt]

will merge this after addressing cruft updates in a different PR