[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Python bindings probs...

From: Joerg Hessdoerfer <Joerg.Hessdoerfer_at_sea-gmbh.com>
Date: 2005-02-15 11:43:09 CET

Hi again!

I just did some more experiments using my own code and Max Bowsher's demo.
(See previous posts from weekend). I'm seeing the following weird behaviour,
and I'd like to ask if this is normal:

- When calling
svn_client_wc_status(...,descend = False, get_all = True, update = False,
no_ignore = False, ...)
I always get the status of the requested path + the status of all the files
and dirs directly in this directory

- When calling
svn_client_wc_status(...,descend = False, get_all = True, update = True,
no_ignore = False, ...)
on a WC path which came from a ra_local repo, I only see the same for the WC
root directory, all calls on any dir deeper in the WC only returns the status
for this directory without it's children.

- When calling the same on a ra_dav based repo I get a segmentation fault.
(Debian testing packages V1.1.3). Traceback:

#0 0xb7d2a5be in svn_auth_set_parameter (auth_baton=0x0, name=0x0, value=0x0)
at subversion/libsvn_subr/auth.c:144
#1 0xb7907217 in svn_ra_dav__do_check_path ()
from /usr/lib/libsvn_ra_dav-1.so.0
#2 0xb7980668 in svn_client__open_ra_session (session_baton=0x0, ra_lib=0x0,
base_url=0x0, base_dir=0x0, base_access=0x0,
    commit_items=0x0, use_admin=1, read_only_wc=1, ctx=0x81df710,
pool=0x81df6d8) at subversion/libsvn_client/ra.c:276
#3 0xb7984caa in svn_client_status (result_rev=0xbffff3d4, path=0xb7dee0c4
"/tmp/test-wc",
    revision=0x81d2be0, status_func=0xb7d5830e <svn_swig_py_status_func>,
status_baton=0xb762bbc4, descend=1, get_all=1, update=1,
    no_ignore=0, ctx=0x81df710, pool=0x81df6d8) at
subversion/libsvn_client/status.c:190
#4 0xb7da7272 in init_client ()
from /usr/lib/python2.3/site-packages/libsvn/_client.so
#5 0x080fde6a in PyCFunction_Call ()
#6 0x080ab834 in PyEval_CallObjectWithKeywords ()
#7 0x080a9bee in Py_MakePendingCalls ()
#8 0x080aa77c in PyEval_EvalCodeEx ()
#9 0x080fd9b7 in PyStaticMethod_New ()
#10 0x0805b989 in PyObject_Call ()
#11 0x080ab5c7 in PyEval_CallObjectWithKeywords ()
#12 0x080a0df6 in _PyBuiltin_Init ()
#13 0x080fde6a in PyCFunction_Call ()
#14 0x080ab834 in PyEval_CallObjectWithKeywords ()
#15 0x080a9bee in Py_MakePendingCalls ()
#16 0x080aa77c in PyEval_EvalCodeEx ()
#17 0x080ab8e9 in PyEval_CallObjectWithKeywords ()
#18 0x080ab72c in PyEval_CallObjectWithKeywords ()
#19 0x080a9bee in Py_MakePendingCalls ()
#20 0x080aa77c in PyEval_EvalCodeEx ()
#21 0x080acf79 in PyEval_EvalCode ()
#22 0x080d90db in PyRun_FileExFlags ()
#23 0x080d885f in PyRun_SimpleFileExFlags ()
#24 0x08054e95 in Py_Main ()
#25 0x080549eb in main ()

It looks like something more needs initialization. Can someone tell me what
and how to do it?

I'm really trying to get this running, not trying to be obnoxious.

Thanks,
 Jrg

-- 
Leading SW developer  - S.E.A GmbH
Mail: joerg.hessdoerfer@sea-gmbh.com
WWW:  http://www.sea-gmbh.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Feb 15 11:44:19 2005

This is an archived mail posted to the Subversion Dev mailing list.