[issue8100] `configure` incorrectly handles empty OPT variable

Benjamin Peterson added the comment: 2010/3/10 Arfrever Frehtes Taifersar Arahesis : > > Arfrever Frehtes Taifersar Arahesis added the > comment: > > Could you apply this patch also in 3.1 branch? Done. -- ___ Python tracker

[issue8100] `configure` incorrectly handles empty OPT variable

Arfrever Frehtes Taifersar Arahesis added the comment: Could you apply this patch also in 3.1 branch? -- ___ Python tracker ___ ___ Py

[issue8100] `configure` incorrectly handles empty OPT variable

Changes by Benjamin Peterson : -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue8100] `configure` incorrectly handles empty OPT variable

Changes by Benjamin Peterson : -- versions: -Python 2.7, Python 3.1, Python 3.2 ___ Python tracker ___ ___ Python-bugs-list mailing li

[issue8100] `configure` incorrectly handles empty OPT variable

Benjamin Peterson added the comment: Fixed in r78817. -- assignee: -> benjamin.peterson nosy: +benjamin.peterson ___ Python tracker ___ _

[issue8100] `configure` incorrectly handles empty OPT variable

Changes by Brett Cannon : -- priority: -> low stage: -> patch review type: -> behavior ___ Python tracker ___ ___ Python-bugs-list m

[issue8100] `configure` incorrectly handles empty OPT variable

New submission from Arfrever Frehtes Taifersar Arahesis : The comment in configure.in says that some changes aren't applied to OPT variable when OPT variable has been set by the user, but they are applied when empty OPT has been explicitly set. The attached patch fixes this problem. -