[MacPorts] #32840: python portgroup: strange results from python_get_version

[MacPorts]

#32840: python portgroup: strange results from python_get_version
--------------------------------------+-------------------------------------
  Reporter:  ryandesign@…             |       Owner:  macports-tickets@…                   
      Type:  defect                   |      Status:  reopened                             
  Priority:  Normal                   |   Milestone:                                       
 Component:  ports                    |     Version:  2.0.3                                
Resolution:                           |    Keywords:                                       
      Port:  python                   |  
--------------------------------------+-------------------------------------
Changes (by macports-trac@…):

  * status:  closed => reopened
  * resolution:  invalid =>


Comment:

 This is a new behavior, probably brought about by the change

 # $Id: python-1.0.tcl 88880 2012-01-14 09:20:05Z jmr at macports.org $

 that invalidates some previously-sort-of-working portfiles.

 It causes "port info all" to abort if not called as "port -p info all".
 It is reasonable to expect "port info all" to work at all times.

 This problem affects the following ports in the same way ("Error: Unable
 to open port: can't read "python.version": no such variable"):

 < py-bpython
 < py-docx
 < py-htmldocs
 < py-nose
 < py-transaction
 < py-urlwatch

 There is also an anomaly with the way py-apsw is treated: its python-
 version variants show up in the results for "port info" but not for "port
 list".

 Would it be possible to roll back the change to the group file until
 affected ports and the python-1.0 group file have been brought into
 harmony?  This would seem to be a faster route to fixing the breakage than
 waiting on maintenance of six or seven portfiles.

-- 
Ticket URL: <https://trac.macports.org/ticket/32840#comment:14>
MacPorts <http://www.macports.org/>
Ports system for Mac OS