search

felipec / git-remote-hg

Transparent bidirectional bridge between Git and Mercurial for Git
GNU General Public License v2.0
369 stars 87 forks source link

A bit of python 3 compatibility #71

Closed azmeuk closed 3 years ago

azmeuk commented 6 years ago

In prevision for the day mercurial will support python3. Made with pylint --py3k git-remote-hg. Not everything is fixed yet.

pirat89 commented 6 years ago

This repo is non-active. Try to check https://github.com/mnauw/git-remote-hg which is currently the most active one.

felipec commented 8 months ago

@pirat89 I don't know what you are talking about. This project has python 3 compatibility and it's superior to the one in mnauw's fork.

pirat89 commented 8 months ago

Hi @felipec, check please dates. In time I wrote the comment, there were number of problems regarding python3 (and mercurial for py3) that have been fixed (at least some of them) in mauw's fork and that time if I remember well, we couldn't get any response here, and asking around I've found the fork, where have been some fixes to make the tool working again. Last commit that time was from 2016, my comment above is from 2018 and later that year (or the next one?) some activity appeared here. I can remember something wrong after ~6y. Anyway, I am considering it closed chapter.

felipec commented 8 months ago

Hi @felipec, check please dates. In time I wrote the comment, there were number of problems regarding python3 (and mercurial for py3) that have been fixed (at least some of them) in mauw's fork and that time if I remember well, we couldn't get any response here, and asking around I've found the fork, where have been some fixes to make the tool working again.

I did check the date: May of 2018. In mnauw's fork python3 support was not added until June of 2020. And python3 was not officially supported in Mercurial until November of 2019.

My objection really was with the "this repo is non-active" comment. Yes, it wasn't active at the moment, because I was doing other things, but that didn't mean it wasn't going to become active again.

This project would have more consistent support if people submitted their improvements instead of creating yet another fork. As it stands I'm pretty much the one that has to do everything, so yeah: things invariably are going to take time.