django-threadlocals stopped working upgrading from django 1.11 to django 2.1.3












0















I'm trying to upgrade for a project the django framework from 1.11 to 2.13.



The project depends on django-threadlocals.
(https://github.com/benrobster/django-threadlocals).



After upgrade, request is not set by threadlocals middleware anymore
so any call to




threadlocals.get_current_user()



threadlocals.get_current_request()




returns None



Did not find any issue on github
Have you any hints?
I'm running python 3.5.2










share|improve this question


















  • 1





    Django changed the way middleware works - and the setting name - in version 1.9, and the old way was removed in 2.0. But that library has not been updated in years. Really using threadlocals is not recommended anyway, you should almost certainly find a better way of doing whatever it is you are trying to do.

    – Daniel Roseman
    Nov 28 '18 at 11:59
















0















I'm trying to upgrade for a project the django framework from 1.11 to 2.13.



The project depends on django-threadlocals.
(https://github.com/benrobster/django-threadlocals).



After upgrade, request is not set by threadlocals middleware anymore
so any call to




threadlocals.get_current_user()



threadlocals.get_current_request()




returns None



Did not find any issue on github
Have you any hints?
I'm running python 3.5.2










share|improve this question


















  • 1





    Django changed the way middleware works - and the setting name - in version 1.9, and the old way was removed in 2.0. But that library has not been updated in years. Really using threadlocals is not recommended anyway, you should almost certainly find a better way of doing whatever it is you are trying to do.

    – Daniel Roseman
    Nov 28 '18 at 11:59














0












0








0








I'm trying to upgrade for a project the django framework from 1.11 to 2.13.



The project depends on django-threadlocals.
(https://github.com/benrobster/django-threadlocals).



After upgrade, request is not set by threadlocals middleware anymore
so any call to




threadlocals.get_current_user()



threadlocals.get_current_request()




returns None



Did not find any issue on github
Have you any hints?
I'm running python 3.5.2










share|improve this question














I'm trying to upgrade for a project the django framework from 1.11 to 2.13.



The project depends on django-threadlocals.
(https://github.com/benrobster/django-threadlocals).



After upgrade, request is not set by threadlocals middleware anymore
so any call to




threadlocals.get_current_user()



threadlocals.get_current_request()




returns None



Did not find any issue on github
Have you any hints?
I'm running python 3.5.2







python django django-2.1






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 28 '18 at 11:08









Andrea BisogninAndrea Bisognin

11




11








  • 1





    Django changed the way middleware works - and the setting name - in version 1.9, and the old way was removed in 2.0. But that library has not been updated in years. Really using threadlocals is not recommended anyway, you should almost certainly find a better way of doing whatever it is you are trying to do.

    – Daniel Roseman
    Nov 28 '18 at 11:59














  • 1





    Django changed the way middleware works - and the setting name - in version 1.9, and the old way was removed in 2.0. But that library has not been updated in years. Really using threadlocals is not recommended anyway, you should almost certainly find a better way of doing whatever it is you are trying to do.

    – Daniel Roseman
    Nov 28 '18 at 11:59








1




1





Django changed the way middleware works - and the setting name - in version 1.9, and the old way was removed in 2.0. But that library has not been updated in years. Really using threadlocals is not recommended anyway, you should almost certainly find a better way of doing whatever it is you are trying to do.

– Daniel Roseman
Nov 28 '18 at 11:59





Django changed the way middleware works - and the setting name - in version 1.9, and the old way was removed in 2.0. But that library has not been updated in years. Really using threadlocals is not recommended anyway, you should almost certainly find a better way of doing whatever it is you are trying to do.

– Daniel Roseman
Nov 28 '18 at 11:59












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


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53518048%2fdjango-threadlocals-stopped-working-upgrading-from-django-1-11-to-django-2-1-3%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.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53518048%2fdjango-threadlocals-stopped-working-upgrading-from-django-1-11-to-django-2-1-3%23new-answer', 'question_page');
}
);

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







Popular posts from this blog

A CLEAN and SIMPLE way to add appendices to Table of Contents and bookmarks

Calculate evaluation metrics using cross_val_predict sklearn

Insert data from modal to MySQL (multiple modal on website)