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 yan12125
Recipients brett.cannon, serhiy.storchaka, skrah, vstinner, xdegaye, yan12125
Date 2017-04-22.12:31:26
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1492864286.37.0.462319788747.issue29442@psf.upfronthosting.co.za>
In-reply-to
Content
I guess you were asking whether the newly compiled Python binary is able to build extension modules or not? I rebased PR 139 against the latest git master and seems it's fine. Running `make distclean`, `./configure` and then `make` builds all modules as expected. The result is the same on Travis CI and Appveyor.

About "elegant": I guess the only issue regarding elegancy in my patch is the local import in  GNUTranslations._parse(). For me moving setup.py away from deprecated modules is a good reason for introducing local imports. Does it sound OK?
History
Date User Action Args
2017-04-22 12:31:26yan12125setrecipients: + yan12125, brett.cannon, vstinner, skrah, xdegaye, serhiy.storchaka
2017-04-22 12:31:26yan12125setmessageid: <1492864286.37.0.462319788747.issue29442@psf.upfronthosting.co.za>
2017-04-22 12:31:26yan12125linkissue29442 messages
2017-04-22 12:31:26yan12125create