Comments (6)
a) Sorry for not replying earlier (see http://reinout.vanrees.org/weblog/2012/03/20/github-email-notifications.html for the reason...)
b) You even need such a setuptools-x for the latest subversion now as the .svn layout changed again.
c) The best solution is to just add a MANIFEST.in. The latest zest.releaser suggests such a file to you if you miss it, precisely because even svn starts acting up now. The suggested MANIFEST.in should fit most usecases, so it is not as scary as it was a couple of years ago.
So I'm leaning to not warning about setuptools-x, but we could theoretically add an "...or install setuptools-git" message to our MANIFEST.in suggestion. And suppress the warning if setuptools-git is installed.
What's your opinion?
And Maurits (co-author), what do you think?
from zest.releaser.
@do3cc Does the above change sound good?
from zest.releaser.
Sounds good to me. Thanks!
from zest.releaser.
I have released zest.releaser 3.34 today.
from zest.releaser.
Hi,
today I saw an e-mail from Alex Grönholm, asking why setuptools-git is in my setup_requires. Before I answered him I wanted to verify my assumption that an egg with setuptools-git in setup_requires does NOT install setuptools-git when only installing the egg with easy_install or pip. Unfortunately it DOES install setuptools-git. That should not be needed on production systems. So I start to believe, the MANIFEST.in warning might be more appropriate.
from zest.releaser.
Hi Patrick,
The MANIFEST.in warning/suggestion is what zest.releaser is doing currently, so I guess nothing needs changing here, unless you have suggestions for a better text in that suggestion.
Let me see if I can explain the difference between setup.requires and install_requires.
Packages in the setup_requires need to be available before the setup.py can be handled correctly. Theoretically, this may lead to a chicken and egg problem, where the setup_requires need to be installed before you can determine what the setup_requires are... This is one of the reasons why work is being done in core Python to move away from setup.py and towards a declarative setup.cfg.
When you easy_install a package:
- its source gets downloaded,
- easy_install reads the setup.py looking for setup_requires (or maybe it can also get some info from PyPI for this),
- it installs packages that are in the setup_requires list, and then
- it installs the install_requires and the package itself.
In a (Plone) buildout, when you add a package to the eggs of your instance, only the package and its install_requires end up in the created instance script. The setup_requires get installed 'somewhere', but not in the instance script. You see this with some ZopeSkel templates: when you have created such a package in src/my.package/ and you use this in a buildout, then a PasteScript egg and a few other eggs get installed within the src/my.package/ directory.
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.