Comments (5)
Well, we could mention it. But I don't regard them as mandatory. The poreleaser is very handy, agreed.
But both setuptools packages are better replaced with a proper MANIFEST.in file.
Maurits? Nice advertising opportunity for zest.poreleaser :-)
from zest.releaser.
I think better be safe than sorry. You probably don't lose anything having those deps there...?
from zest.releaser.
Well, you invite mistakes by others that don't use the buildout. With a MANIFEST.in you're covered.
And: I dislike having unneeded things lying around. It is a bit untidy, imho. So in that sense it is a loss.
But if you (or Maurits) can phrase it as a suggestion or configuration example, it won't really hurt. Could you fork and make the change? That's easier for me to say 'yes' to :-) :-) I'm lazy, which is why I made zest.releaser :-)
from zest.releaser.
Well, I have seen setuptools-subversion slow things down because it does an 'svn ls', which needs to talk to the server. So I am not sure if I still have that package installed currently.
And setuptools-bzr should logically also be added, but last time I checked it, it was broken. I don't remember if it could not be installed or if it simply failed when you tried to make a release in a bazaar checkout.
So: -1 on adding these as hard dependencies.
We could add these as an extra_requires in the setup.py and point to this in the readme.
from zest.releaser.
Closing this, as the discussion has ended
from zest.releaser.
Related Issues (20)
- index-servers vs. index_servers HOT 3
- postrelease minor/patch version HOT 6
- Passing version as a command-line parameter to `prerelease` and `fullrelease` HOT 2
- Unexpected `prerelease` behaviour with Changelog containing markdown links HOT 2
- Documentation: hook_package_dir en entrypoints section.
- support [tool:zest.releaser] in setup.cfg HOT 2
- support pep621 HOT 4
- Future plans for zest.releaser HOT 4
- Prefixing git tags with a "v" HOT 2
- Check version for PEP440 HOT 3
- bumprelease functionality HOT 6
- zest.releaser with plone.releaser breaks when not in a buildout.coredev environment HOT 3
- Failed git push does not fail release HOT 6
- Possibility to add prefix to commit messages HOT 6
- ValueError: binary mode doesn't take an encoding argument HOT 9
- fullrelease: error: no such option: --no-input HOT 8
- sdist is missing tox.ini HOT 1
- tests fails with non-GNU ls HOT 4
- testing: the following arguments are required: message HOT 1
- testing: bumpversion and postrelease tests fails HOT 3
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 zest.releaser.