-
Notifications
You must be signed in to change notification settings - Fork 20
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
Drop Pygments dependency #76
Comments
The problem is that we use pygments at nodes. But yeah, I agree, we should remove it from dependencies... |
is the |
We use pygments for few things.
I'm against removing it since core code depends on that. |
and the mimetype guessing is used for? |
for determining type of fileNode. |
It's not the vcs core functionality and I would actually prefer removing it... Dnia 14 wrz 2011 o godz. 01:22 Marcin Kuźmińskireply@reply.github.com napisał(a):
|
ok, but maybe just do pygment imports in those functions, and raise explanatory exception why ex. "install pygments for this to function" or something like that... |
That could work, but in fact, it's not core vcs functionality as it's not repository management related. Mimetypes etc should be computed at the higher level. I'd go with:
|
Sounds good to me. On Fri, Sep 16, 2011 at 13:25, Lukasz Balcerzak
|
vcs/utils/helpers.py:get_highlighted_code(...)
and thevcs/utils/annotate.py
module don't seem to be used so it seems to me that the Pygments dependency could be dropped from the install scripts.The text was updated successfully, but these errors were encountered: