This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author pitrou
Recipients brett.cannon, eric.snow, ncoghlan, pitrou, python-dev, scoder, superluser
Date 2017-05-29.07:14:32
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Ok, I did an experiment. I added "from __future__ import absolute_import" at the top of _multidict.c, and after a recompile the warning went away.

What changed was that the following line:

  __pyx_t_1 = __Pyx_Import(__pyx_n_s_sys, 0, -1); if (unlikely(!__pyx_t_1)) __PYX_ERR(0, 5, __pyx_L1_error)

was replaced with:

  __pyx_t_1 = __Pyx_Import(__pyx_n_s_sys, 0, 0); if (unlikely(!__pyx_t_1)) __PYX_ERR(0, 3, __pyx_L1_error)

Ignore the change from "3" to "5", which is the line number for the traceback.  The relevant change is the "level" argument to __Pyx_Import() which went from -1 to 0.
Date User Action Args
2017-05-29 07:14:33pitrousetrecipients: + pitrou, brett.cannon, ncoghlan, scoder, python-dev, eric.snow, superluser
2017-05-29 07:14:33pitrousetmessageid: <>
2017-05-29 07:14:33pitroulinkissue25791 messages
2017-05-29 07:14:32pitroucreate