ok this was my fault... easy_e17 has `python` hardcoded into it -- after changing to `python2` all was well.
but it still seems to me that the hashbang of editje should respect the $PYTHON build variable; i'm happy to submit a patch for this if acceptable. C Anthony On Sun, Feb 6, 2011 at 4:52 AM, C Anthony Risinger <[email protected]> wrote: > Oh yeah, it would be spectacular if $PYTHON was written to editje-bin > shebang... archlinux is py3k by default so any variation of `python` doesn't > work; we have a python2 binary that I export for building. > > C Anthony [mobile] > > On Feb 6, 2011 2:51 AM, "C Anthony Risinger" <[email protected]> wrote: >> hello, >> >> i use a small ~20 line wrapper around the easy_e17 script to create >> rolling builds every few days or so. editje (which is incredible btw) >> would always fail during `make install` with this: >> >> ----------------------------------------------------------------------- >> >> Making install in editje >> make[1]: Entering directory `/var/cache/easy_e17/e17_src/editje/editje' >> make[2]: Entering directory `/var/cache/easy_e17/e17_src/editje/editje' >> make[2]: Nothing to be done for `install-exec-am'. >> test -z >> "/opt/.e17/2011-02-05-1296943259/lib/python2.7/site-packages/editje" >> || /bin/mkdir -p >> "/opt/.e17/2011-02-05-1296943259/lib/python2.7/site-packages/editje" >> /bin/install -c -m 644 __init__.py about.py log_window.py >> actions_box.py animations.py clist.py collapsable.py colorpicker.py >> rpc_handlers.py controller.py desktop.py desktop_handler.py >> desktop_part_handlers.py desktop_part_listener.py >> desktop_parts_manager.py details.py details_group.py details_part.py >> details_state.py details_widget.py details_widget_actionslist.py >> details_widget_boolean.py details_widget_button.py >> details_widget_button_list.py details_widget_color.py >> details_widget_combo.py details_widget_entry.py >> details_widget_entry_button.py details_widget_entry_button_list.py >> details_widget_font.py details_widget_signals.py >> details_widget_source.py details_widget_states.py editable.py >> editable_animation.py editable_part.py editable_program.py >> editable_state.py editje.py edjecc.py >> '/opt/.e17/2011-02-05-1296943259/lib/python2.7/site-packages/editje' >> /bin/install -c -m 644 error_notify.py event_manager.py >> fileselector.py filewizard.py floater.py floater_opener.py >> groupselector.py misc.py objects_data.py openfile.py operation.py >> parts.py popup_win.py popups.py prop.py signals.py swapfile.py >> sysconfig.py widgets_list.py >> '/opt/.e17/2011-02-05-1296943259/lib/python2.7/site-packages/editje' >> Traceback (most recent call last): >> File "/usr/lib/python2.7/site.py", line 553, in <module> >> main() >> File "/usr/lib/python2.7/site.py", line 535, in main >> known_paths = addusersitepackages(known_paths) >> File "/usr/lib/python2.7/site.py", line 268, in addusersitepackages >> user_site = getusersitepackages() >> File "/usr/lib/python2.7/site.py", line 243, in getusersitepackages >> user_base = getuserbase() # this will also set USER_BASE >> File "/usr/lib/python2.7/site.py", line 232, in getuserbase >> from sysconfig import get_config_var >> ImportError: cannot import name get_config_var >> make[2]: *** [install-pkgpythonPYTHON] Error 1 >> make[2]: Leaving directory `/var/cache/easy_e17/e17_src/editje/editje' >> make[1]: *** [install-am] Error 2 >> make[1]: Leaving directory `/var/cache/easy_e17/e17_src/editje/editje' >> make: *** [install-recursive] Error 1 >> >> ----------------------------------------------------------------------- >> >> which usually occurs due to unresolvable circular imports. my >> LD_LIBRARY_PATH and PYTHONPATH look like this: >> >> # echo -e "PY: $PYTHONPATH\nLD: $LD_LIBRARY_PATH" >> PY: /opt/e17/lib/python2.7/site-packages: >> LD: /opt/e17/lib: >> >> where /opt/e17 is symlinked to a specific time-based build: >> >> # ls -l /opt/ >> e17 -> .e17/2011-02-05-1296900590 >> >> this way it is very easy for me to rollback to other build simply by >> moving a symlink. >> >> anyways... when i unset PYTHONPATH right before the build, everything >> works fine. i'm trying to figure out if this due to my wrapper, >> easy_e17, enlightenment, or python (2.7). the first two seem very >> unlikely, as the issue is reproducible for me simply by cd'ing into >> the src dir and manually issuing a `make install` once the entire >> build is complete. >> >> any ideas here? would it be appropriate for src/editje/py-compile to >> unset this, or why is this causing a circular import to begin with? >> i'm running archlinux, and i don't think i've manually changed >> anything concerning python. >> >> thanks, >> >> C Anthony > ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ enlightenment-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-users
