-
Notifications
You must be signed in to change notification settings - Fork 2.4k
manimce
to manim
& capitalizing Manim in readme
#794
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why don't you also edit the pyproject.toml
and also update the lock file using poetry lock
command after editing? Or else on release things will be uploaded only to manimce
and not manim
.
docs/source/installation/win.rst
Outdated
@@ -12,7 +12,7 @@ You can install manim very easily using chocolatey, by typing the following comm | |||
|
|||
.. code-block:: powershell | |||
|
|||
choco install manimce | |||
choco install manim |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please revert this line. It's manimce
only, because of some version issue manim
is deprecated on chocolatey, so it is correct to say manimce
here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
okay, I will change it back to manimce. will this change in future?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Only after we do a 1.0.0
release it will change.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ok
Regarding the color change of code literals: I don't mind the current color scheme; I'm open to experiments. Just some general comments off the top of my head:
|
We could also make both orange and the links could be underlined. But I'd prefer to distinguish the only highlighted things form the linked things in a way, and I think that bold would also look quite nice and easy to distinguish and I also like the idea of making it similar to the ones here on GitHub. |
I've now also made the change in pyproject.toml , and there are now lots of changes in poetry.lock. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks good to me so far. There are further occurrences in the current master branch that are not modified here:
version_num = pkg_resources.get_distribution("manimce").version
in the twitter template (master needs to be merged in here for this to work)(either using ``pip install manimce`` or with Chocolatey)
introubleshooting.rst
asset_name: manimce-${{ steps.tag.outputs.tag }}.tar.gz
inpython-publish.yml
The first two occurrences should definitely be changed; I'm not sure about the third one.
# Conflicts: # pyproject.toml
ok, I also updated this now, however, I have no idea of what this does. @eulertour : can you tell us if this should be changed? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this is done.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Left a few non-blocking comments; maybe leave the PR open for a little while longer before merging, in case anyone else has something to add about it.
@@ -47,5 +47,5 @@ jobs: | |||
with: | |||
upload_url: ${{ steps.create_release.outputs.upload_url }} # This pulls from the CREATE RELEASE step above, referencing it's ID to get its outputs object, which include a `upload_url`. See this blog post for more info: https://jasonet.co/posts/new-features-of-github-actions/#passing-data-to-future-steps | |||
asset_path: dist/*.tar.gz | |||
asset_name: manimce-${{ steps.tag.outputs.tag }}.tar.gz | |||
asset_name: manim-${{ steps.tag.outputs.tag }}.tar.gz |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think that this will require an update from @Groctel for the AUR pkgbuild at https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=manimce#n36 -- but if I read the pkgbuild correctly, it will have to be updated for the new release anyways, so not actually a problem.
<a href="http://choosealicense.com/licenses/mit/"><img src="https://img.shields.io/badge/license-MIT-red.svg?style=flat" alt="MIT License"></a> | ||
<a href="https://www.reddit.com/r/manim/"><img src="https://img.shields.io/reddit/subreddit-subscribers/manim.svg?color=orange&label=reddit" alt="Reddit" href=></a> | ||
<a href="https://github.com/psf/black"><img src="https://img.shields.io/badge/code%20style-black-000000.svg" alt="Code style: black"> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Comment, non-blocking: I'm not sure whether we actually need a black
badge in our readme, but won't block the PR because of it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
same idea here, that was inspired by other repos:
https://github.com/pandas-dev/pandas
<a href="https://discord.gg/mMRrZQW"><img src="https://img.shields.io/discord/581738731934056449.svg?label=discord&color=yellow" alt="Discord"></a> | ||
<a href="https://manimce.readthedocs.io/en/latest/"><img src="https://readthedocs.org/projects/manimce/badge/?version=latest" alt="Documentation Status"></a> | ||
<a href="https://hub.docker.com/r/manimcommunity/manim"><img src="https://img.shields.io/docker/v/manimcommunity/manim?color=%23099cec&label=docker%20image" alt="Docker image"> </a> | ||
<a href="https://pepy.tech/project/manim"><img src="https://pepy.tech/badge/manim/month?" alt="Downloads"> </a> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Comment, non-blocking: Same with this, download stats aren't something I as a (potential) user would be interested in.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it gives nice feedback about how often this repo is used, and I was inspired by other repos that have this badge as well:
https://github.com/matplotlib/matplotlib
https://github.com/pandas-dev/pandas
I'd rather merge it now so that manim on pypi can be updated. |
I think as we have now a new Pypi location, we should update the readme and the docs.
Further, at the moment there was some inconsistency in Capitalization in the readme that is now fixed as well.
One further thing I might add to this PR is another highlighting colour in the docs for everything that goes into " ` " , as I don't like the orange and red words together in one part:EDIT: For a later pr