Skip to main content

my-xonsh-fork is to convert your xonsh fork package name to the new
i.e. xonsh becomes xonsh42 and you can run it, add it to shebang or import in python.

How it works

  1. You have your own fork of original xonsh repository.
  2. You want to install it on your host. But you don't want to lose the original xonsh on your host. You don't want to rename xonsh package in your fork code to have an ability to pull the changes from the original xonsh repository without conflicts.
  3. When you run my-xonsh-fork it make a clone of the source git repo and replaces xonsh directory, calls, paths with the xonsh{FORK_NAME} i.e. xonsh2.
  4. Then you can install this package using pip.
  5. As result you'll have xonsh on the host along with xonsh2. You can use both xonsh and xonsh2 in the sheband of your scripts i.e. #!/usr/bin/env xonsh2.
  6. Enjoy! :)

Install

pip install my-xonsh-fork

Usage

usage: my-xonsh-fork [-h] -n FORK_NAME -s SOURCE_REPO [-t TARGET_REPO] -d TARGET_DIR [-f]

Convert your xonsh fork package name to the new.

optional arguments:
  -h, --help            show this help message and exit
  -n FORK_NAME, --fork-name FORK_NAME
                        Fork name i.e. `-n 2` will create `xonsh2` fork.
  -s SOURCE_REPO, --source-repo SOURCE_REPO
                        Source repo i.e. git@github.com:anki-code/xonsh-xep-2.git
  -t TARGET_REPO, --target-repo TARGET_REPO
                        Target empty repo to push the result i.e. git@github.com:anki-code/xonsh2.git
  -d TARGET_DIR, --target-dir TARGET_DIR
                        Target dir i.e. /tmp/xonsh2
  -f, --force-rebuild   Remove XONSH_TARGET_DIR and rebuild from scratch.

Example

For example you want to have two packages: xonsh with original xonsh and xonsh2 - your fork of original xonsh.

To achieve this here is the example based on XEP-2 fork:

my-xonsh-fork -n 2 -s git@github.com:anki-code/xonsh-xep-2.git -d /tmp/xonsh2 -f
pip install -U /tmp/xonsh2
xonsh2 --no-rc

If you want to push the renamed fork to new repo use --target-repo argument.

.xonshrc, rc.xsh and xontrib

If your fork has name 2 (i.e. my-xonsh-fork -n 2 ...) then the new names of RC files and xontrib command will be: .xonshrc_2, rc_2.xsh and xontrib2.

Metadata

Release files for my-xonsh-fork 0.0.3

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for my-xonsh-fork 0.0.3
File Size Uploaded Provenance Actions
my-xonsh-fork-0.0.3.tar.gz 3.7 kB Without provenance Details for my-xonsh-fork-0.0.3.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for my-xonsh-fork 0.0.3
File Interpreter ABI Platform Actions
my_xonsh_fork-0.0.3-py3-none-any.whl Python 3 none any Details for my_xonsh_fork-0.0.3-py3-none-any.whl

Total release size: 7.5 kB

Release files / my-xonsh-fork-0.0.3.tar.gz

Download URL my-xonsh-fork-0.0.3.tar.gz
Size 3.7 kB
Tags Source
SHA-256 checksum
How to use checksums
d3010062cac27afe6871e5df7a7e7d1af905db11ed4a120e2c47a30cb1e1a44c
BLAKE2b-256 checksum
How to use checksums
dd1f37e666de0302a28e19a2b90289a49a6380a7a323ac0fba02433daf093d50
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/3.2.0 pkginfo/1.6.1 requests/2.24.0 setuptools/49.2.1 requests-toolbelt/0.9.1 tqdm/4.51.0 CPython/3.9.0

Release files / my_xonsh_fork-0.0.3-py3-none-any.whl

Download URL my_xonsh_fork-0.0.3-py3-none-any.whl
Size 3.8 kB
Tags Python 3
SHA-256 checksum
How to use checksums
ec4a1ebe958efd73c6b21b00d2935ff3f5189698f2220dbe524279cf94621e4c
BLAKE2b-256 checksum
How to use checksums
f56f9f8631c62d80d9de2acb7eae33692b77a982b318d023021cb54e94d02564
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/3.2.0 pkginfo/1.6.1 requests/2.24.0 setuptools/49.2.1 requests-toolbelt/0.9.1 tqdm/4.51.0 CPython/3.9.0

Security for my-xonsh-fork 0.0.3

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release

0.0.3 This release

2 release files No provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page