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

Drop Pygments dependency #76

Open
jonashaag opened this issue Aug 29, 2011 · 9 comments
Open

Drop Pygments dependency #76

jonashaag opened this issue Aug 29, 2011 · 9 comments

Comments

@jonashaag
Copy link
Contributor

vcs/utils/helpers.py:get_highlighted_code(...) and the vcs/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.

@lukaszb
Copy link
Member

lukaszb commented Sep 13, 2011

The problem is that we use pygments at nodes. But yeah, I agree, we should remove it from dependencies...

@jonashaag
Copy link
Contributor Author

is the lexers attribute required for core functionality? or is it just for some user interface stuff?

@marcinkuzminski
Copy link
Member

We use pygments for few things.

  • highlight of code for helper functions
  • lexers to gues mimetypes

I'm against removing it since core code depends on that.

@jonashaag
Copy link
Contributor Author

and the mimetype guessing is used for?

@marcinkuzminski
Copy link
Member

for determining type of fileNode.
When you fetch a file from repository at given revision method .mimetype will return type of file.

@lukaszb
Copy link
Member

lukaszb commented Sep 14, 2011

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):

for determining type of fileNode.
When you fetch a file from repository at given revision method .mimetype will return type of file.

Reply to this email directly or view it on GitHub:
#76 (comment)

@marcinkuzminski
Copy link
Member

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...

@lukaszb
Copy link
Member

lukaszb commented Sep 16, 2011

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:

  1. Remove pygments from deps, raise exception when trying to use pygments-based methods (like mimetype, lexer etc)
  2. Mark those methods as deprecated
  3. Remove in the next 2 releases (before final release)

@marcinkuzminski
Copy link
Member

Sounds good to me.
Marcin Kuzminski

On Fri, Sep 16, 2011 at 13:25, Lukasz Balcerzak
reply@reply.github.com
wrote:

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:

  1. Remove pygments from deps, raise exception when trying to use pygments-based methods (like mimetype, lexer etc)
  2. Mark those methods as deprecated
  3. Remove in the next 2 releases (before final release)

Reply to this email directly or view it on GitHub:
#76 (comment)

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

3 participants