Pierre-Yves Chibon

Gentle ping? I'm really curious to know if others are thing this or if I'm doing something wrong :)

Indeed, I even increased the ``time.sleep`` to 2 seconds but if I print ``print(com.oid.hex, com.commit_time)`` line 99, I get: ```` 6ecf8698c6c4cc294b5a9be4b550d10e53afdbc7 2b708aaaf85ef0f7913db61f9c14489f79844b7b 42da3d707d2d69799705174b6fed4bd6bed66aa1 Commit #3 42da3d707d2d69799705174b6fed4bd6bed66aa1 1514211183 Commit #1 6ecf8698c6c4cc294b5a9be4b550d10e53afdbc7...

Git blame shows this line changed 5 years ago, but that behavior did not exist in: ``python-pygit2-0.24.2-1.el7.x86_64 libgit2-0.24.6-2.el7.x86_64`` which is from November 2016, odd :s

Ok, so thanks to your input and hint about the commit date/time I was able to find the issue in my code (well tests in this case), turns out my...

It did not have the same behavior, adding the time.sleep(1) should make that behavior consistent, still need to confirm it though. Would you like to keep the ticket open to...

> You are only sorting by time, so there cannot be a guaranteed order between commits with the same timestamp. Any order among them is correct and equivalent. But shouldn't...

So what would be the proper way to ask?

At least I can confirm that using ```` $ cat test_pygit2.py #!/usr/bin/env python import tempfile import time import os import pygit2 path = tempfile.mkdtemp(prefix='pygit2_test_') repo = pygit2.init_repository(path) author = pygit2.Signature('Alice...

Seeing the commit timestamp I wondered if this could be related to changes in git itself, one host is using: ``git-1.8.3.1-12.el7_4.x86_64`` while the other is using: ``git-2.14.3-3.fc27.x86_64``

Something like: http://www.pygit2.org/objects.html#creating-commits ?