Mocking with ldap3: TypeError: 'NotImplementedType' object is not callable
1
I'm trying to run the example for mocking with ldap3 from the documentation:
$ python3
Python 3.5.3 (default, Sep 27 2018, 17:25:39)
[GCC 6.3.0 20170516] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> from ldap3 import Server, Connection, MOCK_SYNC
>>> server = Server('my_fake_server')
>>> connection = Connection(server, user='cn=my_user,ou=test,o=lab',password='my_password',client_strategy=MOCK_SYNC)
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "/usr/lib/python3/dist-packages/ldap3/core/connection.py", line 270, in __init__
self.strategy = MockSyncStrategy(self)
TypeError: 'NotImplementedType' object is not callable
Does anyone know why this fails?
python mocking ldap3
asked Nov 23 '18 at 9:34
loris
13713
add a comment |
1
I'm trying to run the example for mocking with ldap3 from the documentation:
$ python3
Python 3.5.3 (default, Sep 27 2018, 17:25:39)
[GCC 6.3.0 20170516] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> from ldap3 import Server, Connection, MOCK_SYNC
>>> server = Server('my_fake_server')
>>> connection = Connection(server, user='cn=my_user,ou=test,o=lab',password='my_password',client_strategy=MOCK_SYNC)
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "/usr/lib/python3/dist-packages/ldap3/core/connection.py", line 270, in __init__
self.strategy = MockSyncStrategy(self)
TypeError: 'NotImplementedType' object is not callable
Does anyone know why this fails?
python mocking ldap3
asked Nov 23 '18 at 9:34
loris
13713
Perhaps you are using a old version of ldap3. Which version is this?
– Mauro Baraldi
Nov 23 '18 at 18:51
1
Good point. It's ldap3 version 1.2.2, which is the current version available as a package for Debian 9.6. However, I see that, Debian being Debian, 1.2.2 is over 2 1/2 years old and the current version of ldap3 is 2.5.1. After updating to ldap3 2.5.1 via pip the error disappears. Thanks!
– loris
Nov 26 '18 at 8:57
add a comment |
1
1
1
I'm trying to run the example for mocking with ldap3 from the documentation:
$ python3
Python 3.5.3 (default, Sep 27 2018, 17:25:39)
[GCC 6.3.0 20170516] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> from ldap3 import Server, Connection, MOCK_SYNC
>>> server = Server('my_fake_server')
>>> connection = Connection(server, user='cn=my_user,ou=test,o=lab',password='my_password',client_strategy=MOCK_SYNC)
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "/usr/lib/python3/dist-packages/ldap3/core/connection.py", line 270, in __init__
self.strategy = MockSyncStrategy(self)
TypeError: 'NotImplementedType' object is not callable
Does anyone know why this fails?
python mocking ldap3
asked Nov 23 '18 at 9:34
loris
13713
I'm trying to run the example for mocking with ldap3 from the documentation:
$ python3
Python 3.5.3 (default, Sep 27 2018, 17:25:39)
[GCC 6.3.0 20170516] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> from ldap3 import Server, Connection, MOCK_SYNC
>>> server = Server('my_fake_server')
>>> connection = Connection(server, user='cn=my_user,ou=test,o=lab',password='my_password',client_strategy=MOCK_SYNC)
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "/usr/lib/python3/dist-packages/ldap3/core/connection.py", line 270, in __init__
self.strategy = MockSyncStrategy(self)
TypeError: 'NotImplementedType' object is not callable
Does anyone know why this fails?
python mocking ldap3
python mocking ldap3
asked Nov 23 '18 at 9:34
loris
13713
asked Nov 23 '18 at 9:34
loris
13713
edited Nov 23 '18 at 10:08
asked Nov 23 '18 at 9:34
loris
13713
asked Nov 23 '18 at 9:34
loris
13713
asked Nov 23 '18 at 9:34
loris
13713
13713
Perhaps you are using a old version of ldap3. Which version is this?
– Mauro Baraldi
Nov 23 '18 at 18:51
1
Good point. It's ldap3 version 1.2.2, which is the current version available as a package for Debian 9.6. However, I see that, Debian being Debian, 1.2.2 is over 2 1/2 years old and the current version of ldap3 is 2.5.1. After updating to ldap3 2.5.1 via pip the error disappears. Thanks!
– loris
Nov 26 '18 at 8:57
add a comment |
Perhaps you are using a old version of ldap3. Which version is this?
– Mauro Baraldi
Nov 23 '18 at 18:51
1
Good point. It's ldap3 version 1.2.2, which is the current version available as a package for Debian 9.6. However, I see that, Debian being Debian, 1.2.2 is over 2 1/2 years old and the current version of ldap3 is 2.5.1. After updating to ldap3 2.5.1 via pip the error disappears. Thanks!
– loris
Nov 26 '18 at 8:57
Perhaps you are using a old version of ldap3. Which version is this?
– Mauro Baraldi
Nov 23 '18 at 18:51
Perhaps you are using a old version of ldap3. Which version is this?
– Mauro Baraldi
Nov 23 '18 at 18:51
1
1
Good point. It's ldap3 version 1.2.2, which is the current version available as a package for Debian 9.6. However, I see that, Debian being Debian, 1.2.2 is over 2 1/2 years old and the current version of ldap3 is 2.5.1. After updating to ldap3 2.5.1 via pip the error disappears. Thanks!
– loris
Nov 26 '18 at 8:57
Good point. It's ldap3 version 1.2.2, which is the current version available as a package for Debian 9.6. However, I see that, Debian being Debian, 1.2.2 is over 2 1/2 years old and the current version of ldap3 is 2.5.1. After updating to ldap3 2.5.1 via pip the error disappears. Thanks!
– loris
Nov 26 '18 at 8:57
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53443986%2fmocking-with-ldap3-typeerror-notimplementedtype-object-is-not-callable%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
draft saved
draft discarded
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53443986%2fmocking-with-ldap3-typeerror-notimplementedtype-object-is-not-callable%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Perhaps you are using a old version of ldap3. Which version is this?
– Mauro Baraldi
Nov 23 '18 at 18:51
1
Good point. It's ldap3 version 1.2.2, which is the current version available as a package for Debian 9.6. However, I see that, Debian being Debian, 1.2.2 is over 2 1/2 years old and the current version of ldap3 is 2.5.1. After updating to ldap3 2.5.1 via pip the error disappears. Thanks!
– loris
Nov 26 '18 at 8:57