From: David S. <on...@gm...> - 2013-11-10 15:06:55
|
On Sun, 10 Nov 2013 15:40:39 +0100 Davide Andreoli <da...@gu...> wrote: > 2013/11/10 David Seikel <on...@gm...> > > > On Sat, 09 Nov 2013 13:19:46 +0200 Kai Huuhko <kai...@gm...> > > wrote: > > > > > 09.11.2013 07:28, David Seikel kirjoitti: > > > > On Thu, 17 Oct 2013 16:28:04 +0300 Kai Huuhko > > > > <kai...@gm...> wrote: > > > > > > > >> 17.10.2013 13:50, David Seikel kirjoitti: > > > >>> On Thu, 17 Oct 2013 13:12:25 +0300 Kai Huuhko > > > >>> <kai...@gm...> wrote: > > > >>> > > > >>>> > > > >>>> > > > >>>> 17.10.2013 09:52, David Seikel kirjoitti: > > > >>>>> On Thu, 17 Oct 2013 00:59:20 +0300 Kai Huuhko > > > >>>>> <kai...@gm...> wrote: > > > >>>>> > > > >>>>>> 15.10.2013 15:03, Kai Huuhko kirjoitti: > > > >>>>>>> 15.10.2013 08:45, David Seikel kirjoitti: > > > >>>>>>>> On Mon, 14 Oct 2013 23:31:08 +0300 Kai Huuhko > > > >>>>>>>> <kai...@gm...> wrote: > > > >>>>>>>> > > > >>>>>>>>> Let's just bump the minimum version requirement > > > >>>>>>>>> already. ;) > > > >>>>>>>> > > > >>>>>>>> Ubuntu LTS still has cython 0.15.1. Will I ever be able > > > >>>>>>>> to actually compile any of this python stuff? > > > >>>>>>> > > > >>>>>>> Patience, young Padawan. > > > >>>>>>> > > > >>>>>>> You may ask or wait for us to package the pre-generated > > > >>>>>>> module C source files. > > > >>>>>>> > > > >>>>>>> I believe they recently added a target directory for the > > > >>>>>>> generated files making it easier for us to do development > > > >>>>>>> snapshots; Dave: could we automate this with Jenkins? > > > >>>>>> > > > >>>>>> First step of project onefanged python is complete: we can > > > >>>>>> now create a source tarball with a single command. DaveMDS > > > >>>>>> is now working on adding this step to Jenkins. > > > >>>>>> > > > >>>>>> Using this tarball you'll get the Python modules built > > > >>>>>> without needing Cython at all. > > > >>>>> > > > >>>>> That wont help this onefang numbskull at all, he compiles > > > >>>>> from git. > > > >>>>> > > > >>>> > > > >>>> The barstand! > > > >>>> > > > >>>> Can't you modify the script to use these automated snapshots? > > > >>> > > > >>> Well I could, but I don't want to start special casing stuff > > > >>> in my generic build script. Then every one will want it. :-P > > > >>> > > > >>>> The alternative is for us to keep the generated files in a > > > >>>> branch, which can get messy. > > > >>> > > > >>> That wont work either, my generic build script specifically > > > >>> uses the master branch. > > > >>> > > > >>>> (Or, we'll simply ignore you.) > > > >>> > > > >>> That's "worked" for years. :-P > > > >>> > > > >>> The big problem for me is that I have another project that > > > >>> uses python, and it's important for that project to build on > > > >>> stock standard Ubuntu LTS. So I can't just install the > > > >>> latest cython and be done with it. No doubt when Ubuntu LTS > > > >>> gets refreshed next year, EFL python's cython version > > > >>> requirement will move out of reach. Again. > > > >>> > > > >> > > > >> Not going to happen. Saucy already has Cython 0.19 and that's > > > >> what we're planning to target here. We could go with 0.17 as > > > >> well since we already worked around the problems that 0.18 and > > > >> 0.19 solve. The version bump would simply mean that we can get > > > >> rid of these "hacks". > > > >> > > > >>> I might see if I can simply install the latest cython in some > > > >>> special place, then put that in the path for my EFL build > > > >>> script. > > > >>> > > > >> > > > >> Let me know how that works out. We'll have to figure out > > > >> something else if it doesn't work. > > > > > > > > It half worked. I installed cython 0.19.1 from git source into > > > > my home directory. Modified my build script to include that > > > > install in the various python paths. The build works, but when > > > > I sudo to root (using sudo -E to replicate the environment > > > > variables) to run the install, it claims to not be able to find > > > > a recent enough cython. I checked the python paths from sudo, > > > > they are the same. > > > > > > > > I don't have enough python fu to debug this. > > > > > > Weird... maybe a relative path somewhere that gets mangled by > > > sudoing? I'll change the setup script to output the actual > > > exception thrown. Hopefully the traceback from it can tell us > > > what's going on. > > > > For some odd reason sudo was dropping PYTHONPATH, even though my > > version of PYTHONINCLUDE was getting through correctly. > > > > Now it seems to be installing, but the "python setup.py install" > > command is returning an error code, even though no errors are in the > > logs. The final build log entries are - > > > > running install_egg_info > > Removing /opt/e17/lib/python2.7/site-packages/efl-1.7.99-py2.7.egg-info > > Writing /opt/e17/lib/python2.7/site-packages/efl-1.7.99-py2.7.egg-info > > > > Has it actually finished? > > > > Yes, that one is the last line of a successfully install, but here the > command > exit with a correct "0" status. > > Your /opt/e17/lib/python2.7/site-packages/efl/ folder should contain > the .so files, the __init__.py and 2 folders (elementary and utils) > with other .so files. Yes it does. > Once installed you can try the bindings using the test provided in the > "examples" > folder in the sources. > cd examples/elementary > python test.py That works. > probably you need to set PYTHONPATH to include the folder you actually > install to. Hmm, it does already. PYTHONPATH=/media/btrfs/home/dvs1/e17_svn/cython:/opt/e17/lib/python2.7/site-packages: Guess that's an overall success then. B-) -- A big old stinking pile of genius that no one wants coz there are too many silver coated monkeys in the world. |