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

Error #3

Closed
Fale opened this issue Dec 7, 2016 · 2 comments · Fixed by #4
Closed

Error #3

Fale opened this issue Dec 7, 2016 · 2 comments · Fixed by #4
Assignees

Comments

@Fale
Copy link

Fale commented Dec 7, 2016

If I try to run gitfame on the github.com/ansible/ansible repo:

The following output appears:

Blame:   4%|█████▌                                                                                                                                          | 126/3265 [00:12<09:12,  5.68it/s]Traceback (most recent call last):
  File "/usr/bin/gitfame", line 9, in <module>
    load_entry_point('git-fame==1.1.0', 'console_scripts', 'gitfame')()
  File "/usr/lib/python3.5/site-packages/gitfame/_gitfame.py", line 239, in main
    run(args)
  File "/usr/lib/python3.5/site-packages/gitfame/_gitfame.py", line 181, in run
    auths = RE_AUTHS.findall(blame_out)
TypeError: cannot use a string pattern on a bytes-like object
@casperdcl
Copy link
Owner

Hmm...

$ git clone git@github.com:ansible/ansible
$ cd ansible
ansible (devel)$ git fame
Blame: 100%|████████████████████████████████| 3265/3265 [03:01<00:00, 18.01it/s]

Though I get a different error later related to unicode (on python 2.7). Probably due to unicode characters in author names. I thought I had fixed that. Grr.

@Fale
Copy link
Author

Fale commented Dec 7, 2016

Actually, I used the python3 version (on Python 3.5.2). It could be the same problem that appears in different ways on py2 and py3?

@casperdcl casperdcl self-assigned this Dec 7, 2016
@casperdcl casperdcl mentioned this issue Dec 7, 2016
ciwhiz pushed a commit to ciwhiz/git-fame that referenced this issue Jan 18, 2022
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 a pull request may close this issue.

2 participants