Python 2.7 isn't supported anymore, neither by Superset or Python itself... We run test against 3.6 and recommend that for now.
Max On Thu, Feb 20, 2020 at 8:52 AM Brannon, Terrence <terrence.bran...@usbank.com.invalid> wrote: > Hi Lakshman: > * I did a quick google search for your error message and this Superset > issue came up - https://github.com/apache/incubator-superset/issues/8425 > ... which version of superset are you running? In fact, as a word to > Superset: is there a standard bug reporting format that a user can generate > via a single command to give all details relevant to a problem? > > ALSO: apparently this error occurs with some people who are running 0.35.1 > - > https://stackoverflow.com/questions/59289314/superset-0-35-1-druid-error-name-pydruid-is-not-defined > > * Superset has "deprecated support for Python 2" - > https://superset.incubator.apache.org/installation.html ... why are you > running on Python 2 instead of 3.6? > > -----Original Message----- > From: lakshman pervatoju <lakshman.pervat...@gmail.com> > Sent: Thursday, February 20, 2020 8:28 AM > To: d...@superset.apache.org > Subject: [EXTERNAL] Superset and kerberized Druid cluster > > Hi Everybody, > We have a kerberized druid cluster and have few datasources created. > Installed superset and trying to Load Druid data source and get the below > > "name 'PyDruid' is not defined" > > but I am able to import PyDruid. > The current version of python we have is 2.7.5 > > Note: we have set up Basic authentication for druid and while adding druid > cluster we did provide these credentials. > > Also, looking into how AD authentication and superset work together. > > Appreciate the help. > Thanks in Advance, > > > U.S. BANCORP made the following annotations > --------------------------------------------------------------------- > Electronic Privacy Notice. This e-mail, and any attachments, contains > information that is, or may be, covered by electronic communications > privacy laws, and is also confidential and proprietary in nature. If you > are not the intended recipient, please be advised that you are legally > prohibited from retaining, using, copying, distributing, or otherwise > disclosing this information in any manner. Instead, please reply to the > sender that you have received this communication in error, and then > immediately delete it. Thank you in advance for your cooperation. > > --------------------------------------------------------------------- >
