asweigart / pyperclip

Python module for cross-platform clipboard functions.
https://pypi.python.org/pypi/pyperclip
BSD 3-Clause "New" or "Revised" License
1.6k stars 193 forks source link

Consider tagging releases #234

Open jaraco opened 1 year ago

jaraco commented 1 year ago

I notice that this repo has no tags. That means there are many different commits that correspond to a given release in PyPI. I recently wanted to know what releases might contain the fix for #147, so I went to the merged commit containing the fix (5def6648383e475f217ce92d2ae3986b572f5a6e), but it gave me no indication of what version(s) might contain that fix. After figuring out where the version is stored, I can see that the version at the time that commit was added was 1.8.0, implying that >1.8.0 would include the fix. Still, it would be nice if there were a way to see which commit specifically was the one that was released to PyPI for any given release. Is there any reason not to tag commits with the release numbers?