Apydia Setup Script
percious
First off, the newest setup.py (from the trunk) does not have a
console script in the entry points... Is there a reason for this
change?
Secondly, your docs mention that you need a number of packages
installed for Apydia to work. Why not put entries for those required
packages in your setup.py and let easy_install gtake care of it for
you?
I'm really excited about creating my google docs this way as soon as I
can get it working!
-chris
percious
python setup.py apydia
Daniel Haus
> First off, the newest setup.py (from the trunk) does not have a
> console script in the entry points... Is there a reason for this
> change?
No idea what you're talking about. See
http://apydia.ematia.de/svn/apydia/trunk/setup.py
from line 44 downwards it reads:
entry_points = """
[console_scripts]
apydia = apydia.command:main
[distutils.commands]
apydia = apydia.command:apydia
[...]
Am I missing something here? The latest trunk (r45) works fine for me.
> Secondly, your docs mention that you need a number of packages
> installed for Apydia to work. Why not put entries for those required
> packages in your setup.py and let easy_install gtake care of it for
> you?
I've been wondering about this for some time now. These packages are
optional. I'm not sure if I should force everyone to install every
optional package. If someone uses eg. Textile exclusively, should I
force her to install Markdown?
Please, everyone who's reading this, tell me what you think and what
way you'd prefer.
> I'm really excited about creating my google docs this way as soon as I
> can get it working!
Nice to hear, I hope we can solve your problem soon.
--
Daniel Haus
http://ematia.de
Daniel Haus
> This is also not working with the trunk code:
> python setup.py apydia
What exactly does happen, when you issue this command?
percious
trunk. I got it working, but there are some errors. It does produce
some documentation.
Would you be interested in a bug dump? Perhaps you can download the
trunk to dbsprockets and run
python setup.py apydia
-percious
Daniel Haus
> Sorry about all that, I had d/led the codegen trunk, not the apydia
> trunk. I got it working, but there are some errors. It does produce
> some documentation.
No problem, I'm happy that it works now.
> Would you be interested in a bug dump? Perhaps you can download the
> trunk to dbsprockets and run
> python setup.py apydia
If course I'm interested. I'll have look at it as soon as I find the
time.
Alberto Valverde
> (...)
>
>> Secondly, your docs mention that you need a number of packages
>> installed for Apydia to work. Why not put entries for those required
>> packages in your setup.py and let easy_install gtake care of it for
>> you?
>
> I've been wondering about this for some time now. These packages are
> optional. I'm not sure if I should force everyone to install every
> optional package. If someone uses eg. Textile exclusively, should I
> force her to install Markdown?
>
> Please, everyone who's reading this, tell me what you think and what
> way you'd prefer.
How about using setuptools' "extras_require" argument to setup()? You
could do something like:
setup(...,
extras_require = {
'markdown': ["Markdown"],
'rst': ["docutils"],
...
}
Then one can do "easy_install Apydia[markdown]", etc... to get the
flavor they want, all requirements listed this way are optional.
Alberto
Daniel Haus
> How about using setuptools' "extras_require" argument to setup()? You
> could do something like:
>
> setup(...,
> extras_require = {
> 'markdown': ["Markdown"],
> 'rst': ["docutils"],
> ...
> }
In fact, I already got that:
extras_require = {
"reST": ["docutils >= 0.4"],
"Textile": ["textile >= 2.0"],
"Markdown": ["markdown >= 1.6a"],
},
Maybe putting this into the docs somewhere could help. I really need
to redo the docs...
Daniel Haus
fixed now?