Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add some pictures or video clips to your Readme #1

Open
eabase opened this issue Jan 20, 2022 · 1 comment
Open

Add some pictures or video clips to your Readme #1

eabase opened this issue Jan 20, 2022 · 1 comment

Comments

@eabase
Copy link

eabase commented Jan 20, 2022

There are many REPL replacements and fixers out there, so it would be incredibly more helpful if you could add some screenshots, video clips or dynamic gifs on how this looks and how it's better than others.

Perhaps, more specifically, what are you adding or improving here, that is not already in ipython or bpython ones?

Cheers!

@asmeurer
Copy link
Owner

So far I've basically just been writing this project for me. I use it every day, but I've never written it with one person in mind. This simplifies the design quite a bit as I don't have to worry about configuration or anything like that. You'll also notice that there isn't a setup.py and it isn't in any package manager. I myself just run it directly from the git repo.

I might consider making this something that other people can use, but only if there is genuine interest. If you want to know what this is like, I would suggest just trying it. You can install the dependencies from requirements.txt and start it with ./bin/mypython after cloning the repo.

The README lists all the main features. It's kind of hard to show off things with a picture or video. The most obvious "feature" you would see in a screenshot is the stupid emoji prompts, but those are just a meme, and not really that essential. The main features are things like multiline input and syntax highlighting, but that comes from prompt-toolkit so will be supported equally well by something like IPython. The other main things are default key bindings which I consider to be sane (impossible to show in a screenshot), syntactically correct tokenization for things like parentheses matching (e.g., not treating "(") as a matching pair like IPython does), and a select number of features like ? and a few %magic commands borrowed from IPython, but working in a way that I consider to be clean.

Making this work for other people would entail adding customization and extensibility (which would add a lot of complexity to the code), probably changing a few of the defaults, and adding several features that I don't care about but other people might care about (like some of the IPython %magic commands that I never use). Plus standard maintenance stuff that I've ignored, like packaging, doing releases, making changes to PRs instead of committing directly to master, using the issue tracker, adding documentation, and so on.

I am open to this, but really only if there is someone who is interested in not only using it, but contributing to it as well, as that's the only way I could sustain the extra maintenance burden from the extra complexity. Otherwise, I'm happy with the README just listing the features and explaining what this is. I will always keep it open source, but I'm not really going to advertise it as something that people should use, as that would just be false advertising.

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

No branches or pull requests

2 participants