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 grahamd
Recipients amaury.forgeotdarc, benjamin.peterson, christian.heimes, eric.araujo, grahamd, loewis, ncoghlan, pitrou, python-dev, tarek, vstinner
Date 2011-04-25.22:01:13
SpamBayes Score 3.1321334e-11
Marked as misclassified No
Message-id <1303768874.11.0.0165010318337.issue10914@psf.upfronthosting.co.za>
In-reply-to
Content
Hmmm, I wander if that is related to the workaround I have added in mod_wsgi recently of:

    /*
     * Force loading of codecs into interpreter. This has to be
     * done as not otherwise done in sub interpreters and if not
     * done, code running in sub interpreters can fail on some
     * platforms if a unicode string is added in sys.path and an
     * import then done.
     */

    item = PyCodec_Encoder("ascii");
    Py_XDECREF(item);

This fixes problem some have seen where one gets:

  LookupError: no codec search functions registered: can't find encoding

I haven't been able to reproduce the problem myself so no bug report ever lodged.

Have been told it affects some other embedded systems as well which use sub interpreters but other systems don't employ the workaround that I am now using.
History
Date User Action Args
2011-04-25 22:01:14grahamdsetrecipients: + grahamd, loewis, amaury.forgeotdarc, ncoghlan, pitrou, vstinner, christian.heimes, benjamin.peterson, tarek, eric.araujo, python-dev
2011-04-25 22:01:14grahamdsetmessageid: <1303768874.11.0.0165010318337.issue10914@psf.upfronthosting.co.za>
2011-04-25 22:01:13grahamdlinkissue10914 messages
2011-04-25 22:01:13grahamdcreate