Marown/git-filter-repo
1
0
Fork 0
mirror of https://github.com/newren/git-filter-repo.git synced 2024-07-06 10:22:16 +02:00
Code Issues Packages Projects Releases Wiki Activity
a59e67e791
git-filter-repo/release/setup.py

20 lines
366 B
Python
Raw Normal View History

release: add packaging scripts for uploading to PyPI Signed-off-by: Julian Berman <Julian@GrayVines.com> Signed-off-by: Elijah Newren <newren@gmail.com>
2019-11-16 01:30:45 +01:00
from setuptools import setup
release: tweak packaging scripts for uploading to PyPI Clean up the PyPI dist packages, remove unnecessary files, and streamline the release process: * Avoid adding extra unnecessary files to the repo; setup.py is code and can copy the necessary files into place. * Make sure README.md is included so we don't get an UNKNOWN Description field. * Add a long_description_content_type to avoid parsing errors on the README.md file and rejecting the upload. * Define the license and platform fields so they don't show up as UNKNOWN either. * Remove unnecessary pyproject.toml. This makes sense for most python projects, but since I already have a Makefile with installation rules (because I'm trying to be more compatible with git.git just in case we ever get merged into it), the pyproject.toml file is somewhat duplicative. Sure, the Makefile won't specify the exact versions needed but...meh. * Split the release target of the Makefile into github_release and pypi_release substeps, to allow them to be run semi-independently. Make the pypi_release run a few more steps for me. Signed-off-by: Elijah Newren <newren@gmail.com>
2019-12-26 19:43:24 +01:00
import os
Use setup.py entry_points for installation This should make the installation via pip more robust. On Windows the usage of entry_points will install a wrapper executable for the script that chooses the proper python executable. This essentially makes the script run correctly when called via `git filter-repo` (direct execution via `git-filter-repo` was already fine before). This fixes an issue on Windows, where the git-installation will choose a different python executable than the one indicated by the installation via `pip{x,3} install`. Signed-off-by: Benjamin Motz <benjamin.motz@mailbox.org>
2021-03-09 17:15:42 +01:00
def link_parent(src, target=None):
if target is None:
target = src
setup.py: test for FileExistsError on symlink Multiple runs of setuptools encounter a FileExistsError exception trying to re-symlink the same files. This exception is safe to ignore: the files were already symlinked so the call can be considered successful. Signed-off-by: Sirio Balmelli <sirio@b-ad.ch>
2020-02-11 20:19:01 +01:00
try:
Use setup.py entry_points for installation This should make the installation via pip more robust. On Windows the usage of entry_points will install a wrapper executable for the script that chooses the proper python executable. This essentially makes the script run correctly when called via `git filter-repo` (direct execution via `git-filter-repo` was already fine before). This fixes an issue on Windows, where the git-installation will choose a different python executable than the one indicated by the installation via `pip{x,3} install`. Signed-off-by: Benjamin Motz <benjamin.motz@mailbox.org>
2021-03-09 17:15:42 +01:00
os.symlink(os.path.join("..", src), target)
setup.py: test for FileExistsError on symlink Multiple runs of setuptools encounter a FileExistsError exception trying to re-symlink the same files. This exception is safe to ignore: the files were already symlinked so the call can be considered successful. Signed-off-by: Sirio Balmelli <sirio@b-ad.ch>
2020-02-11 20:19:01 +01:00
except FileExistsError:
pass
Use setup.py entry_points for installation This should make the installation via pip more robust. On Windows the usage of entry_points will install a wrapper executable for the script that chooses the proper python executable. This essentially makes the script run correctly when called via `git filter-repo` (direct execution via `git-filter-repo` was already fine before). This fixes an issue on Windows, where the git-installation will choose a different python executable than the one indicated by the installation via `pip{x,3} install`. Signed-off-by: Benjamin Motz <benjamin.motz@mailbox.org>
2021-03-09 17:15:42 +01:00
fix duplicate setuptools entry point script Signed-off-by: Theodore Ni <3806110+tjni@users.noreply.github.com>
2023-08-12 23:19:31 +02:00
link_parent('README.md')
Use setup.py entry_points for installation This should make the installation via pip more robust. On Windows the usage of entry_points will install a wrapper executable for the script that chooses the proper python executable. This essentially makes the script run correctly when called via `git filter-repo` (direct execution via `git-filter-repo` was already fine before). This fixes an issue on Windows, where the git-installation will choose a different python executable than the one indicated by the installation via `pip{x,3} install`. Signed-off-by: Benjamin Motz <benjamin.motz@mailbox.org>
2021-03-09 17:15:42 +01:00
link_parent('git-filter-repo', 'git_filter_repo.py')
fix duplicate setuptools entry point script Signed-off-by: Theodore Ni <3806110+tjni@users.noreply.github.com>
2023-08-12 23:19:31 +02:00
setup(use_scm_version=dict(root="..", relative_to=__file__))
Reference in New Issue Copy Permalink