Skip to content

Conversation

@pablogsal
Copy link
Member

@pablogsal pablogsal commented Apr 20, 2022

Closes: #12

Currently we only have memray3.X as an entry point but having also
memray as an entry point will make it easier for people with only one
Python version installed and it would make the usage examples from -h
line up with how we actually expect it to be used.

This commit also updates the docs and the README file to simplify the
examples with the new entry point.

@pablogsal pablogsal requested a review from godlygeek April 20, 2022 12:46
@pablogsal pablogsal force-pushed the entry_point branch 2 times, most recently from 7940a06 to 7f584fe Compare April 20, 2022 13:02
Currently we only have `memray3.X` as an entry point but having also
`memray` as an entry point will make it easier for people with only one
Python version installed and it would make the usage examples from -h
line up with how we actually expect it to be used.

This commit also updates the docs and the README file to simplify the
examples with the new entry point.
@godlygeek godlygeek enabled auto-merge (rebase) April 21, 2022 00:09
Copy link
Contributor

@godlygeek godlygeek left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM - I removed some no longer needed parentheticals, and spotted a place where we were unnecessarily using implicit string literal concatenation in setup.lpy

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Should we have a memray entry point?

2 participants