| Request | dataflake.ldapconnection -- question -- by Gustavo Narea |
| Posted on | Aug 28, 2008 12:39 pm |
| Subscribe |
| Comment by Jens Vagelpohl on Aug 30, 2008 7:03 am | |
|
Sure, the 0.3 egg is now on PyPI. |
|
|
|
| Comment by Gustavo Narea on Aug 30, 2008 6:47 am | |
|
Hello, Thanks for fixing that! Could you please release the current revision to PYPI? I've written a LDAP plugin for repoze.who that relies on this code, and which I'm going to release tomorrow, but I would have to delay the release if this fix is not available. Thank you very much in advance. - Gustavo. |
|
|
|
| Resolve by Jens Vagelpohl on Aug 30, 2008 6:22 am | |
|
I can't recall why the original code did not re-use the python-ldap exceptions and all tests run fine with the change, so here it is: http://svn.dataflake.org/viewvc?view=rev&revision=1614 |
|
|
|
| Initial Request by Gustavo Narea on Aug 28, 2008 12:39 pm | |
|
Hello, I'm using fakeldap to test LDAP functionality in my package, but because the exceptions defined by fakeldap don't subclass the relevant ldap exceptions, they're not caught by my application. It seems like the only way to get it working is by except'ing fakeldap exceptions too, but I think this would be an ugly solution because I'd have to insert test-related code in my package. Why not proxy ldap exceptions, or at least subclass them? Thanks in advance, and thanks for making this nice package :) - Gustavo. |
