Roald (ubuntu_demon) schrieb: > Could you please point me to some people who work on the python bindings > ? I might be willing to help on the parts which are of interest to my > research. > Allefant is working on this, he is on irc rather often in the european evening hours. > > Having a volunteer having to approve a python script still sounds like > the best solution to me. > > I would be very interested to learn more about the "restricting python > plans" from someone who is involved with that. Maybe allefant is the guy > to talk to about that ? What is his email ? > We did already have something like this in the old days. Now allefant did implement some restrictions to the stuff you can do with python, these were backported to 1.2.x, too, and should be available in 1.2.4. I think he did use something like savepython or such. Best would be if you directly talked to him about this. You will be able to reach him in the irc chan you did already join yesterday. >>> So here's a list of practical stuff that's not yet clear to me : >>> >>> * if python will be restricted somehow in the future will I be able to >>> turn this of by compiling wesnoth with --unrestricted-python ? >> That seems like a reasonable request, but it will depend on how >> difficult it is to code the python restrictions. > > If someone can tell me whether such a compile switch will be implemented > I won't have to be afraid my stuff suddenly stops working when a new > development version is released (if I chose to work with the development > branch which I'm inclined to). This is important to me. I don't think such a switch is currently planned, more important is: Is this switch really needed? ATM 1.2.x and the dev versions do use exactly the same restrictions for python. > - From the change log it doesn't sound as much has changed regarding the > python API. Don't trust the changelog. Some devs forget to add some/many/all of their changes to the changelog and they only get added if someone does it for them (which is very seldom). So the changelog is only the bare minimum of stuff that was changed, often it is a whole lot more... >> Personally, if I were you, I would use the latest development version >> at the time you actually start doing serious coding. It will probably >> be easier to get devs to make any changes that are needed by you on >> the development branch then on the stable branch. > > Good argument. It probably would be easier to get devs to make any > changes that are needed. And hope if I would make any change myself it > would have a better chance at getting accepted if it's actually nice > code (though I'm no c++ guy). There probably will be close to zero changes to 1.2 so patches for it are likeley not to be applied. So you really should work with the dev versions, maybe even trunk would be best though this can get very tricky to manage in terms of "longer time support" (everything >1 month is a long time in the matter of Wesnoth time shedules).
I hope this helps a little. Cheers, Nils Kneuper aka Ivanovic _______________________________________________ Wesnoth-dev mailing list [email protected] https://mail.gna.org/listinfo/wesnoth-dev
