Menu
▾
▴
python-ldap-dev
|
From: Richard H. <hol...@os...> - 2002-03-28 19:27:24
|
I hope this makes since. It looks like there are three copies of the body of the document in the document. Maybe I can help. Where can I find the tex source for this document? Sincerely, Rick |
|
From: <mi...@st...> - 2002-03-28 21:37:57
|
Richard Holbert wrote: > I hope this makes since. It looks like there are three copies of the body of > the document in the document. I know. I already asked for Latex support on the list. > Maybe I can help. Where can I find the tex source for this document? Best bet is to directly check out from CVS: http://sourceforge.net/cvs/?group_id=2072 Web-Interface: http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/python-ldap/python-ldap/Doc/ Your help's appreciated! Ciao, Michael. |
|
From: <mi...@st...> - 2002-03-29 14:40:02
Attachments:
python-ldap.how
|
Richard Holbert wrote:
>
> Change input{} to include{}...
I've commited a modified python-ldap.tex. However it does not compile (see
attached python-ldap.how). Not sure whether it was ok before...
Ciao, Michael.
|
|
From: <mi...@st...> - 2002-03-29 15:47:17
|
Michael Str=F6der wrote: > Richard Holbert wrote: >=20 >> I think we only need the includes for: >> >> ldap >> ldap_async >> ldap_modlist >> ldif >> and ldapurl >=20 > > The rest should remain as inputs. >=20 > Ok, another commit. > [..] > Still it does not compile. I'm lost with TeX... Uuumh, the problem is that my local ldap.tex gets overwritten after doing= make. Ciao, Michael. |
|
From: <mi...@st...> - 2002-03-29 16:06:38
|
Richard Holbert wrote:
>>
>>>Still it does not compile. I'm lost with TeX...
>>
>>Uuumh, the problem is that my local ldap.tex gets overwritten after doing
>>make.
>
> Mine too, I tried chmod 444 ldap.tex
It is not overwritten if I use \input{ldap}. What's the exact difference of
\input{} and \include{}?
Ciao, Michael.
|
|
From: Rich S. <r....@ve...> - 2002-03-29 16:16:05
|
I do not currently have convenient access to a Unix machine with the Python source, but in a couple of days I should have my Linux box back online. I've written two python manuals -- for ZSI and wizard -- and have basically got it down to a cookbook approach. Take a look at those; for example, you can find PS PDF and HTML for ZSI, generated from the TeX input at http://www.zolera.com/opensrc/zsi If that's of interest, I can fix things up next week. /r$ |
|
From: Jens V. <je...@zo...> - 2002-03-29 16:31:16
|
what i really like about the ZSI TeX sources is that they build with just one small dependency on something created by the actual software building process (version.tex), you don't have to execute any Makefiles to create the docs. that means i can load it into my favorite TeX editor/processor and build it in there without any problem. jens On Friday, March 29, 2002, at 11:16 , Rich Salz wrote: > I do not currently have convenient access to a Unix machine with the > Python source, but in a couple of days I should have my Linux box back > online. I've written two python manuals -- for ZSI and wizard -- and > have basically got it down to a cookbook approach. Take a look at those; > for example, you can find PS PDF and HTML for ZSI, generated from the > TeX input at http://www.zolera.com/opensrc/zsi > > If that's of interest, I can fix things up next week. > /r$ > > > > _______________________________________________ > Python-LDAP-dev mailing list > Pyt...@li... > https://lists.sourceforge.net/lists/listinfo/python-ldap-dev |
|
From: <mi...@st...> - 2002-03-29 17:49:53
|
Jens Vagelpohl wrote:
> what i really like about the ZSI TeX sources is that they build with
> just one small dependency on something created by the actual software
> building process (version.tex), you don't have to execute any Makefiles
> to create the docs.
I glanced over the ZSI doc sources and as far as I understand they are built
exactly the same way like the python-ldap docs. The Makefile looks
somewhat cleaner.
\input{} is used to include the chapters (like also done in the Python docs).
> that means i can load it into my favorite TeX
> editor/processor and build it in there without any problem.
Feel free to fix/clean-up the python-ldap TeX sources to make it loadable
into your favorite TeX editor/processor.
Ciao, Michael.
|
|
From: <mi...@st...> - 2002-03-29 18:00:00
|
Richard Holbert wrote:
> Now it looks like a problem in ldap_async.tex, and ldap_modlist.tex.
>
> I deleted the \input{ldap_async} and \input{ldap_modlist} lines from
> python-ldap.tex
Bingo!
Renamed ldap_async to ldap-async and ldap_modlist to ldap-modlist and it
seems to work now.
I've commited the changes.
Ciao, Michael.
|
|
From: Richard H. <hol...@os...> - 2002-05-09 19:01:11
|
Dear Michael,
I've ran into a problem with the way the exception handler error messages are
returned by python-ldap.
I'm trying to print exception handler error messages using the following:
try:
l.simple_bind_s(login_dn, login_pw)
except ldap.LDAPError, e:
print "BINDFAILED", e
sys.exit(1)
But it doesn't work as expected. Here's what I get:
BINDFAILED {'desc': "Can't contact LDAP server"}
This is because your exception handler returns e is an instance of a
dictionary, so I have to do the following:
try:
l.simple_bind_s(login_dn, login_pw)
except ldap.LDAPError, e:
print "BINDFAILED", e.args[0]['desc']
sys.exit(1)
To get:
BINDFAILED Can't contact LDAP server
The exception handler in IO is a bit more straight forward.
This example:
try:
input = open("config.txt","r")
except IOError, e:
print "CONFIGFILEERROR", e
sys.exit(1)
yields the following:
CONFIGFILEERROR [Errno 2] No such file or directory: 'config.txt'
Thanks!
Rick
|
|
From: Michael <mi...@st...> - 2002-05-09 21:19:09
|
Richard Holbert schrieb:
>
> I've ran into a problem with the way the exception handler error messages are
> returned by python-ldap.
> [..]
> BINDFAILED {'desc': "Can't contact LDAP server"}
>
> This is because your exception handler returns e is an instance of a
> dictionary, so I have to do the following:
> [..]
> The exception handler in IO is a bit more straight forward.
Feel free to contribute an implementation of a __str__() method for the
LDAPError class. Should be in Modules/error.c.
Ciao, Michael.
|
Thanks for helping keep SourceForge clean.
X