Comments (2)
First: Thank you for writing this down, especially usability problems like this are hard to come by because I can't look every user over the shoulder and hear them thinking!
About: bumpversion: error: too few arguments
: That's auto-generated by argparse, because no command line argument was given (and part
is among many others an argument). You're right, this can only be caused by not giving a "part" at the moment. I should probably catch this explicitly and show a nicer error message, before handing things off to argparse.
In the standard configuration, a part is "one of major
, minor
, patch
", however that list is configurable so it might be anything else.
You're right "part" may be an unfortunate name, and it's very well up for discussion. "level" might be better, but I don't think that's to the point. Why is it so hard finding a name for this ?
About your suggestion making "part" optional: That was the default behavior in bumpversion < 0.3, and I made it so because bumping versions is something explicit that you do conciously and I want users to make an explicit choice which part of the version should be bumped.
from bumpversion.
Closing this until someone (maybe me?) comes up with a better name. I'm very open to suggestions!
from bumpversion.
Related Issues (20)
- Multi-line `replace` doesn't work for lines starting with `#` HOT 2
- Missing allowed 'part' values in commandline help HOT 2
- All strings matching current version are bumping up in setup.py file. HOT 2
- Issue while using search and replace configurations. HOT 2
- Do not fail on the dirty state during the dry-run HOT 1
- How to keep the metadata part when bumping version?
- bump version number in filename
- Bumpversion --list returned non-zero exit status 1 HOT 1
- Improvement README.rst
- TypeError: 'NoneType' object is not iterable HOT 1
- Release version from working branch
- search-replace falls back to plain version lookup in some cases HOT 1
- help need: error while serialize following pattern (?P<major>\d+)\.(?P<minor>\d+)\.(?P<patch>\d+)\.(?P<build>\d+)
- No Pre-Release Tags if Major Version is 0 HOT 1
- bumpversion w/ added "commit" part adding additional parts to files
- Add ability to specify a value of a part of version only HOT 1
- Need better documentation on multiline support for `search` and `replace`
- Is it possible to allow {current_[part]} / {new_[part]} in search/replace?
- Dependencies versions in pyproject.toml altered casually
- Is it possible to make numbered beta versions like in npm?
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from bumpversion.