irelease is an Python package to release your package.


Keywords
github-release, pypi, python, release, release-automation, tag
License
MIT
Install
pip install irelease==1.2.0

Documentation

irelease

Python PyPI Version License Forks Open Issues Project Status Downloads Downloads Medium GitHub repo size Donate

Release your library by using the command: irelease or pyrelease

Star this repo if you like it! ⭐️

Introduction

irelease is Python package that will help to release your python package on both github and pypi. A new release of your package is created by taking the following steps:

  1. Extract the version from the init.py file

  2. Remove old build directories such as dist, build and x.egg-info

  3. Git pull (to make sure all is up to date)

  4. Get latest release version at github

  5. Check if the local (current) version is newer then the latest github release.

     1. Make new wheel, build and install package
     2. Set tag to newest version
     3. Push to git
     4. Upload to pypi (credentials for pypi required)
    

Installation

  • Install irelease from PyPI (recommended). irelease is compatible with Python 3.6+ and runs on Linux, MacOS X and Windows.
  • It is distributed under the MIT license.

Quick Start

pip install irelease

Alternatively, install irelease from the GitHub source:

git clone https://github.com/erdogant/irelease.git
cd irelease
python setup.py install

Run irelease

Go to the directory where the package is you want to release and simply run release:

$ irelease

The following arguments are availble:

# Github name
irelease -u <githubname>

# Package name your want to release
irelease -p <packagename>

# Removing local builds:
# 1: Yes
# 0: No
irelease -c 1

# Verbosity messages:
# 0: No messages
# 1: Error only
# 2: Warnings and above
# 3: Regular messages and above
# 4: Debug and above
# 5: Trace and above
irelease -v 5

# Twine path for to irelease at pypi. This is automatically determined if standard installation is performed.
irelease -t 'C://<username>/AppData/Roaming/Python/Python36/Scripts/twine.exe'

Example:

Your package to-be-published must have the correct structure. At least these files and folders are expected:

    <any_dirname>/
    ├── <package_dir>/
    │   ├── __init__.py
    │   ├── package_name.py
    │   ├── ...
    ├── .gitignore
    ├── LICENSE
    ├── README.md
    ├── requirements.txt
    ├── setup.py
    └── ...

Example: releasing bnlearn package.

    bnlearn/
    ├── bnlearn/
    │   ├── __init__.py
    │   ├── bnlearn.py
    ├── .gitignore
    ├── LICENSE
    ├── README.md
    ├── requirements.txt
    ├── setup.py

Go to your destination dir and run release:

$ irelease

release with your specified arguments

# Package can be specified:
$ bnlearn>irelease -p bnlearn

# Username can be specified:
$ bnlearn>irelease -u erdogant

# Cleaning of previous builds in directory can be disabled
$ bnlearn>irelease -c 0

Do not forget to enter some release information on github and mark your release number:

References

Maintainer

  • Erdogan Taskesen, github: erdogant
  • Contributions are welcome.
  • If you wish to buy me a Coffee for this work, it is very appreciated :)