René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"gitdb and gitdb2 on PyPI","articleBody":"In 2015, [access was lost to the PyPI account](https://github.com/gitpython-developers/GitPython/issues/298) that owns [gitdb](https://pypi.org/project/gitdb/).\r\nv0.6.4 was the last release under the gitdb package on PyPI prior to this happening.\r\n\r\nIn 2016, [gitdb2](https://pypi.org/project/gitdb2/) [was created to continue development for the library under a new package](https://github.com/gitpython-developers/GitPython/issues/511) (https://github.com/gitpython-developers/gitdb/commit/38866bc7c4956170c681a62c4508f934ac826469), and every release since then has been with that package name. This has caused confusion (see #45, #47, #57, https://github.com/gitpython-developers/GitPython/issues/983) and having an old, stale PyPI project is less than ideal.\r\n\r\n[Recently, the original PyPI account has been recovered](https://github.com/pypa/pypi-support/issues/204).\r\nThe intention now is to transition back to using the original gitdb package name and have the gitdb2 package simply be a mirror/dummy package that depends on and installs gitdb, so as to maintain backwards compatibility.\r\n\r\nCurrently, these are the anticipated steps that need to be taken:\r\n- [x] ~~Release a new version, v3.0.3, as the gitdb2 package, that restricts the smmap2 version to \u003c 3\r\n(See https://github.com/gitpython-developers/smmap/issues/44)~~\r\n- [x] ~~Release a new version, v4.0.0, as the gitdb package; the only change from gitdb2 v3.0.3 should be to require smmap rather than smmap2 (https://github.com/gitpython-developers/smmap/issues/44)~~\r\n- [x] ~~Create a gitdb2 branch with a single setup.py that requires gitdb~~\r\n- [x] ~~Release a new version, v4.0.0, of the gitdb2 package from the gitdb2 branch~~\r\n  - **Note** Because I (@Byron) accidentally released step 2 in this list as package gitdb2 instead of gitdb, v4.0.0 of gitdb2 already existed. The change requested here is now in v4.0.1.\r\n\r\n~~v4.0.0 for both packages should be functionally equivalent to gitdb2 v3.0.3, with gitdb2 v4.0.0 simply installing gitdb \u003e= 4.0.0 and with gitdb v4.0.0 requiring smmap rather than smmap2 (https://github.com/gitpython-developers/smmap/issues/44).~~\r\n\r\n- [X] gitdb2 v3.0.3 was released with an erroneous and incomplete changelog\r\ngitdb2 v3.0.3.post1 has been [tagged](https://github.com/gitpython-developers/gitdb/releases/tag/3.0.3.post1) and [released on PyPI](https://pypi.org/project/gitdb2/3.0.3.post1/) to fix this\r\n- [X] gitdb v4.0.0 was tagged with the wrong package name and released with an incomplete changelog and unbound smmap requirement version specifiers\r\nThe master branch has been force-pushed to https://github.com/gitpython-developers/gitdb/commit/253dfe7092f83229d9e99059e7c51f678a557fd2 and gitdb v4.0.1 has been [tagged](https://github.com/gitpython-developers/gitdb/releases/tag/4.0.1) and [released on PyPI](https://pypi.org/project/gitdb/4.0.1/)\r\n  - [X] gitdb v4.0.0 has been deleted on PyPI\r\n- [X] gitdb2 improperly branches off of the 4.0.0 tag and includes the entire GitDB library\r\nThe gitdb2 branch has been force-pushed to https://github.com/gitpython-developers/gitdb/commit/d3bf396b54b02122e209a14afa9895e652fce32f to be properly set up for gitdb2 to be a mirror package and the gitdb2-4.0.0 and gitdb2-4.0.1 tags have been deleted\r\n- [X] gitdb2 v4.0.0 was released as the entire GitDB library and without requiring gitdb\r\ngitdb2 v4.0.0 has been deleted on PyPI\r\n- [X] gitdb2 v4.0.1 was released as the entire GitDB library while still requiring gitdb\r\ngitdb2 v4.0.2 has been [released on PyPI](https://pypi.org/project/gitdb2/4.0.2/) from the new gitdb2 branch (https://github.com/gitpython-developers/gitdb/commit/d3bf396b54b02122e209a14afa9895e652fce32f)\r\n  - [X] gitdb2 v4.0.1 has been deleted on PyPI\r\n- [X] A new version of GitPython, v3.1.0, that requires gitdb rather than gitdb2, has been [tagged](https://github.com/gitpython-developers/GitPython/releases/tag/3.1.0) (at first, https://github.com/gitpython-developers/GitPython/commit/c859019afaffc2aadbb1a1db942bc07302087c52 was tagged, but that commit forgot the version bump and as such, it has now been re-tagged to the version bump commit, https://github.com/gitpython-developers/GitPython/commit/8c9da7310eb6adf67fa8d35821ba500dffd9a2a7) and [released on PyPI](https://pypi.org/project/GitPython/3.1.0/)\r\n\r\ngitdb v4.0.1 and gitdb2 v4.0.2 should be functionally equivalent to gitdb2 v3.0.3 with gitdb v4.0.2 simply installing gitdb \u003e= 4.0.1 and with gitdb v4.0.1 requiring smmap rather than smmap2 (https://github.com/gitpython-developers/smmap/issues/44).\r\n\r\nNote: @Byron was having issues with releases, so I was added as a maintainer for gitdb, gitdb2, smmap, and smmap2 on PyPI. Since [there were already issues with the new signature key being used](https://github.com/gitpython-developers/gitdb/issues/55), I've released gitdb v4.0.1, gitdb2 v3.0.3.post1, gitdb2 v4.0.2, smmap v3.0.1, and smmap2 v3.0.1 without any signature keys. The intention is still for @Byron to release new versions with the proper signature key once he has access to it again.","author":{"url":"https://github.com/Harmon758","@type":"Person","name":"Harmon758"},"datePublished":"2020-02-23T00:50:10.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/59/gitdb/issues/59"}