J. David Ibáñez
J. David Ibáñez
There have been major releases of libgit2 (0.99) and pygit2 (1.1); can you try? Such a low level issue is more likely to be from libgit2, so it may be...
For the record I've added s390x to Travis and it's still failing, https://travis-ci.org/github/libgit2/pygit2/jobs/741338976#L1507
In PR #1130 @roehling has fixed a bug related to big endian. Maybe this is the same kind of issue. If someone wants to check...
This looks related to issue #828 If branch names are not allowed to have slashes then it should fail with an informative error, probably `InvalidSpecError` since PR #829 ; did...
That's not the behaviour I observe. If you replace `list(...)` by the for loop you will see many prints. In other words, it's `list` which is blocking, not pygit2. And...
If I'm not missing anything.. These are the places where we use `.data`: - `Blob.data` - `Patch.data` These are the places where we use `.raw`: - `Oid.raw` With `read_raw()`: -...
Good point. No, this doesn't block the release. What I'd like to do before the next release is handling the pycparser issue, #846 The criteria for new releases is: not...
@jnrbsn Okay, noted. The fastest way to get something done is to make a PR.
No, I think it's not implemented. PRs welcome.
We don't support Python 2 any more. Which is the real use case to accept bytes? Maybe there're index files out there that don't use UTF-8?