python-versioneer | version-string management for VCS-controlled trees

by warner Python Version: Current License: No License

X-Ray Key Features Code Snippets Community Discussions(1)Vulnerabilities Install Support

kandi X-RAY | python-versioneer Summary

python-versioneer is a Python library. python-versioneer has no bugs, it has no vulnerabilities, it has build file available and it has low support. You can install using 'pip install python-versioneer' or download it from GitHub, PyPI.

like a rocketeer, but for versions!. Compatible With: python2.6, 2.7, 3.2, 3.3, 3.4, 3.5, 3.6, and pypy. This is a tool for managing a recorded version number in distutils-based python projects. The goal is to remove the tedious and error-prone "update the embedded version string" step from your release process. Making a new release should be as easy as recording a new tag in your version-control system, and maybe making new tarballs.

Support

Quality

Security

License

Reuse

Support

python-versioneer has a low active ecosystem.

It has 716 star(s) with 117 fork(s). There are 23 watchers for this library.

It had no major release in the last 6 months.

There are 75 open issues and 60 have been closed. On average issues are closed in 209 days. There are 15 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of python-versioneer is current.

Quality

python-versioneer has 0 bugs and 0 code smells.

Security

python-versioneer has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

python-versioneer code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

python-versioneer does not have a standard license declared.

Check the repository for any license declaration and review the terms closely.

Without a license, all rights are reserved, and you cannot use the library in your applications.

Reuse

python-versioneer releases are not available. You will need to build from source code and install.

Deployable package is available in PyPI.

Build file is available. You can build the component from source.

Installation instructions, examples and code snippets are available.

python-versioneer saves you 1155 person hours of effort in developing the same functionality from scratch.

It has 2594 lines of code, 205 functions and 39 files.

It has medium code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of python-versioneer

Get all kandi verified functions for this library.

python-versioneer Key Features

No Key Features are available at this moment for python-versioneer.

python-versioneer Examples and Code Snippets

No Code Snippets are available at this moment for python-versioneer.

Community Discussions

Trending Discussions on python-versioneer

How to specify the source (git branch) of a conda build package

QUESTION

How to specify the source (git branch) of a conda build package

Asked 2021-Sep-10 at 16:30

I created a conda package that build successfully, and that I can install with conda. I am using versioneer to automatically generate the version number of my builds. My project is in a git repository with multiple branches.

My problem is that when I want to install the package, conda will install the last built version (no matter the branch), whereas I would like that it installs by default the last version of the branch Master. My workaround is to manually specify the version number of the version I want.

Is there a way to generate a version number with versioneer that will make conda install in priority the last built version of the branch master? Alternatively, is there a way to specify conda the branch to get the latest build?

Thanks

...

ANSWER

Answered 2021-Sep-10 at 16:30

Rather than varying the version, I'd suggest looking into encoding the branch info into either the build string or the label/subdirectory. To me, these seem more semantically consistent with the situation.

Build Variants

For the former, this could either be done explicitly by defining a build string that includes some jinja-templated variable coordinated with the Git branch, or automatically through variants defined in the conda_build_config.yaml. If you get this working, then installing a build from branch foo would go something like:

Source https://stackoverflow.com/questions/69133151

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install python-versioneer

pip install versioneer to somewhere to your $PATH. add a [versioneer] section to your setup.cfg (see below). run versioneer install in your source tree, commit the results.
pip install versioneer to somewhere to your $PATH
add a [versioneer] section to your setup.cfg (see below)
run versioneer install in your source tree, commit the results
See [INSTALL.md](./INSTALL.md) for detailed installation instructions.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: