Re: [pygccxml-development] Installing from cvs doesn't work
Brought to you by:
mbaas,
roman_yakovenko
From: Roman Y. <rom...@gm...> - 2006-04-11 07:34:21
|
On 4/11/06, Matthias Baas <ba...@ir...> wrote: > Roman Yakovenko wrote: > ok, I'll give it a try... Thank you. If you don't have time, we can do it for next release. > Where do you want to keep the version number? Did you just put it into > __init__.py so that it is available somewhere during creating the > distribution or is this also meant as a way for the user to determine > the version at runtime? The first one. Until now I did not get requests to expose version as public variable. If it will be requested I will do that. > Maybe the documentation should be packaged separately. It would be ok to > add them to the sources but I'm not aware that there is a standard > location to install them. I did not add documentation to the sources. The structure I propose is next= : __next_release__ / package_name + version number / setup.py docs / examples / unittests / package / only sources needed to use package + scripts So if you run setup.py it will install only the package, nothing more. If you run release_builder.py you will see it. > - Matthias - -- Roman Yakovenko C++ Python language binding http://www.language-binding.net/ |