here's a detailed proposal for the setup.cfg format. I've included all remarks,
and tried to make the syntax as simple as possible. I've dropped the
stuff and the template language stuff. (people can do it as a
A/ Config file structure:
conditional-sections: one, two
2/ Execution environment:
python_version = '%s.%s' % (sys.version_info, sys.version_info)
os_name = os.name
platform = sys.platform
uname = os.uname()
python_version_info = sys.version_info
comp_op: '<'|'>'|'=='|'>='|'<='|'<>'|'!='|'in'|'not' 'in'|'is'|'is' 'not'
comparison: expr (comp_op expr)*
or_test: and_test ('or' and_test)*
and_test: not_test ('and' not_test)*
not_test: 'not' not_test | comparison
distutils will interpret [setup] and act upon, to fill the
Distribution object and its metadata attribute object.
It will look only for Metadata fields and ignores the others.
In case an option is passed in setup.py, it overrides the one in setup.cfg.
Let me know if it's good enough. I won't write a PEP for this change,
and I will just push it for information at python-dev as soon as I get
enough +1 :)
Tarek Ziadé | http://ziade.org | オープンソースの岩！
So I'm quite sure stdeb is the tool for "py2deb" I'm looking for.
What are the "correct" steps of installing this tool, assuming
Ubuntu9.04. I guess I need this:
1. Python (check)
2. distutils (check)
3. setuptools (dunno? how do I install?)
4. stdeb (how do I install correctly?)
As all of you know by now, I'm fairly new to distutils, PyPI, eggs,
cheesecake, setuptools and stdeb. It's a whole new universe! :)
Hi - I feel like I'm in maze of twisty passages trying to get my SIP/PyQt
extension to play nicely with distutils. Most of the package is pure Python,
but I have one standard C extension and a new SIP one I have added to the
I need to be able to compile C++ files with the compiler and all its
arguments specified for the SIP extension. Is there any way to do this with
distutils? I've gone through the sourcecode and can't see an obvious way to
do this without hacking it completely. distutils compiles C++ files with gcc
(not g++) and uses invalid compiler arguments on this Ubuntu system.
Alternatively, SIP makes a nice Makefile which works. Can I run make as part
of the build process and add the object file to distutils list of files to
Are there any better options than distutils?
I'm new at the mailing list. I write small games in Python/PyGame. I
want to find a way to make a downloadable package/installer/script
to put on my webpage, especially for Ubuntu users.
I've skimmed a couple of tutorials on how to generate .deb-files, but,
wow, it's a whole new skill set to do that!
Does anyone have any hint on a more economic way of creating
single-file distribution packages for Python+PyGame projects? Maybe
some GUI-tool that automates the .deb file creation process, but
targetting Python specifically and not C++.
I've looked at Ubuntu's PPA system, didn't find it end-user-friendly enough.
Also, the Quickly project was too invasive on the way I like to develop
software (it took over the bzr/lp tools; I want to control that).
We are now ready to release 0.6.2. If you feel that there is a critical
bug we should fix before this, this is your last chance.
Python 2.3 compatibility was restored in the latest changeset, so feel
free to test that too.
The next Distribute version will be released soon, with python 3
support (thanks to Martin, Lennart, and Alex !)
and more bug fixed. (you can follow that in the issue tracker)
If you want to give a hand on testing the next Distribute version,
I've uploaded a dev version of the trunk of Distribute at
nightly.ziade.org, meaning that you can try the upcoming release
(at your own risks ;) )
- the tarball : http://nightly.ziade.org/distribute-0.6.2dev.tar.gz
- a modified distribute_setup.py script that will install the dev
version : http://nightly.ziade.org/distribute_setup_dev.py
- a modified bootstrap.py file that will let you bootstrap a
zc.buildout environment with this version
Any feedback would be greatly appreciated,
Tarek Ziadé | http://ziade.org | オープンソースはすごい!
I had a buildout.cfg which I changed to start:
Re-running the buildout doesn't appear to make sure existing eggs that
have been downloaded are unzipped. Is that to be expected?
Simplistix - Content Management, Batch Processing & Python Consulting
[original mail from python-dev
On Tue, Sep 22, 2009 at 03:21:06PM +0200, Tarek Ziadé wrote:
> The pseudo-grammar is (I don't know how to write those but you'll
> get it hopefully)::
> comp: '<'|'>'|'=='|'>='|'<='|'<>'|'!='|'in'|'not' 'in'
> comparison: expr (comp_op expr)*
> expr: STRING
> test: or_test
> or_test: and_test ('or' and_test)*
> and_test: not_test ('and' not_test)*
> not_test: 'not' not_test | comparison
Here you're re-introducing '<', '>', '<=' and '>=' while you said 
that you where going to drop them. I'm still not convinced of
allowing this between strings as it will likely lead to mistakes when
comparing "versions". I'm still tempted by making "python_version" a
RationalVersion() so that you can use '<', '>', '<=' and '>=' safely,
not really convinced of writing something like:
[setup:python_version == '2.2' or python_version == '2.3' or
python_version == '2.4']
(Can you even split section headers over multiple lines in ini-files?)
As an asside, python 3 is dropping '<>' so maybe it would be
easier/less confusing to just not include it here?
Debian GNU/Linux -- The Power of Freedom
www.debian.org | www.gnu.org | www.kernel.org
Lennart Regebro kirjoitti:
> 2009/9/23 Alex Grönholm <alex.gronholm(a)nextday.fi>:
>> I'm not sure what you mean. I don't remember receiving any such things from
>> you, nor is it in the 0.6 branch.
> There are tons of patches in the 0.6 branch. That's why we wanted them tested.
Yes, but did you or did you not commit such changes to the repository?
If not, where can I find these patches so that I might apply them?
At least easy_install does not have the --user option added, which is
necessary for this to work.