Re: [elinks-dev] where to handle python version mismatches?

On May 13, 2008, at 10:17pm, Kalle Olavi Niemitalo writes: >I think we should copy this code snippet from the public-domain >PEP 353 : > >#if PY_VERSION_HEX < 0x0205 && !defined(PY_SSIZE_T_MIN) >typedef int Py_ssize_t; >#define PY_SSIZE_T_MAX INT_MAX >#

Re: [elinks-dev] Remove current_url parameter of Python goto_url_hook?

On Jan 04, 2007, at 10:03pm, Kalle Olavi Niemitalo writes: > I've been thinking of adding radio buttons >"Open in: (o) this tab, ( ) new tab, ( ) new window" to the >"Go to URL" dialog, perhaps even with a "[ ] reload" check box. >If we wanted to pass this data to the goto_url_h

Re: [elinks-dev] Remove current_url parameter of Python goto_url_hook?

On Jan 01, 2007, at 6:58pm, Kalle Olavi Niemitalo writes: >I applied the patch as 26473f72f59641aa60277f14f703f8a76dda5a82, >so that users of snapshots will notice it and can complain if >they don't like it. Sounds good. I think it should be straightforward for a snapshot user to fix hooks.py (by

Re: [elinks-dev] Remove current_url parameter of Python goto_url_hook?

On Dec 31, 2006, at 11:30am, Kalle Olavi Niemitalo writes: >src/scripting/python/hooks.c (script_hook_url) calls hooks as >goto_url_hook(new-url, current-url) and follow_url_hook(new-url). >It has a comment saying that the current-url parameter exists >only for compatibility and that the script can

[elinks-dev] [patch] Use document->cached in src/scripting/python/document.c

For consistency, here's a patch for the Python backend to match last week's change to the Lua backend (in commit 7db8abf6e7ff43f059c4496e734c17337487db2c) that accompanied the fix for bug 756. src/scripting/python/document.c | 13 - 1 files changed, 8 insertions(+), 5 deletions(-)

[elinks-dev] Re: [patch] additional functionality for Python backend

On Nov 27, 2006, at 12:56am, Kalle Olavi Niemitalo writes: >I think convenience for users is more important here than >consistent look. [...] > >I would thus be inclined to install the file as is, at least >until users request a different format. That sounds fine to me, and I certainly won't mind

[elinks-dev] Re: [patch] additional functionality for Python backend

On Nov 26, 2006, at 12:33pm, Kalle Olavi Niemitalo writes: >Thanks; committed as 0c1ba7306f4175c65baad77595f7854bafe6d67e. > >However, doc/Makefile does not yet do anything with python.txt. >"make install-doc" converts many other documents to HTML or PDF >and installs them. As python.txt is appare

[elinks-dev] Re: [patch] additional functionality for Python backend

On Nov 22, 2006, at 11:37pm, Kalle Olavi Niemitalo writes: >Is it OK to add your name and/or email address (as shown above) >to the ELinks source repository (and copies worldwide) as the >author of this patch and any you post later? Yes, you have my permission to do so. Thank you!

Re: [elinks-dev] Re: [patch] additional functionality for Python backend

On Oct 19, 2006, at 3:28pm, Witold Filipczyk writes: >Applied. If you have any enhancements, feel free to send it here. I finally found time to update my repository, and it appears the documentation changes from my patch (removing contrib/python/README.Python and adding doc/python.txt to replace i

[elinks-dev] Re: [patch] additional functionality for Python backend

On Sep 20, 2006, Kalle Olavi Niemitalo writes: >"M. Levinson" writes: >> The patch includes documentation for Python programmers in doc/python.txt, >> and the documentation is also available internally from Python code via >> Python's introspection API. > &

[elinks-dev] Re: [patch] additional functionality for Python backend

On Sep 21, 2006, Kalle Olavi Niemitalo writes: >I get a preprocessor error and reverting the quoted patch fixes it. Hmm, I was trying to follow this advice from doc/hacking.txt: "Please keep includes in alphabetical order unless a specific order is required for compilation on weird systems (then p

Re: [elinks-dev] [patch] some fixes for the Python scripting backend

On Jul 26, 2006, at 7:25am, "M. Levinson" writes: >On Jul 24, 2006, at 7:01pm, Witold Filipczyk writes: >>If you know Python could you say why >>$ valgrind elinks >>shows a lot of errors in the Python part of code? > >I'll be happy to take a look if I can

Re: [elinks-dev] [patch] some fixes for the Python scripting backend

On Jul 24, 2006, at 7:01pm, Witold Filipczyk writes: >Thanks! Applied all but the configure.in part. Could you send configure.in diff >against current GIT version? Sure, and sorry for the trouble. Below is an updated patch against this morning's git tree. >If you know Python could you say why >$

[elinks-dev] Re: [patch] some fixes for the Python scripting backend

On Jul 24, 2006, at 8:06pm, Kalle Olavi Niemitalo writes: >"M. Levinson" <[EMAIL PROTECTED]> writes: > >> 4. ./configure --with-python didn't work because the Python tests were >>trying an incorrect library name and didn't produce all the necessa

[elinks-dev] [patch] some fixes for the Python scripting backend

Included below is a minor reworking of the Python scripting backend to address four issues: 1. Errors (including informative tracebacks) are now presented by calling the report_scripting_error() function in src/scripting/scripting.c. Also, a trivial change to report_scripting_error(): When