Opened 6 years ago

Closed 6 years ago

#57789 closed defect (fixed)

py27-photutils @0.5_0 - build failure

Reported by: majoc-at-astro (majoc-at-astro) Owned by: mf2k (Frank Schima)
Priority: Normal Milestone:
Component: ports Version: 2.5.4
Keywords: Cc:
Port: py-photutils

Description

Photutils builds successfully for Python 3.5 and 3.6, but with Python 2.7 .... 

:info:build ERROR: Photutils requires Python 3.5 or later

I enclose the obvious patch for the Portfile. Please let me know if you require the full logfile. Apologies for CCing the wrong persons.

Attachments (1)

py-photutils.portfile.patch​ (354 bytes) - added by majoc-at-astro (majoc-at-astro) 6 years ago.

Download all attachments as: .zip

Change History (7)

Changed 6 years ago by majoc-at-astro (majoc-at-astro)

Attachment: py-photutils.portfile.patch​ added

comment:1 Changed 6 years ago by mf2k (Frank Schima)

Port: py-photutils added

comment:2 Changed 6 years ago by mf2k (Frank Schima)

Cc: cdeil lpsinger removed

Please only Cc the port maintainers. If there are none, don't Cc anyone.

Last edited 6 years ago by mf2k (Frank Schima) (previous) (diff)

comment:3 Changed 6 years ago by mf2k (Frank Schima)

The py-graveyard port also needs to be updated.

comment:4 in reply to:  2 Changed 6 years ago by majoc-at-astro (majoc-at-astro)

Replying to mf2k:

Please only Cc the port maintainers. If there are none, don't Cc anyone.

Apologies. In future, should I ping macports-dev instead? --- I've had tickets languish for lack of a CC.

comment:5 Changed 6 years ago by mf2k (Frank Schima)

Submitting a GitHub pull request is the best way to get things committed quickly.

comment:6 Changed 6 years ago by mf2k (Frank Schima)

Owner: set to mf2k
Resolution: → fixed
Status: new → closed

In cad68cd10e9a5799ff17f11e8fb8d50e157e8842/macports-ports (master):

py-photutils: Update to version 0.6

  • Add license
  • Use GitHub portgroup
  • Improve long description
  • Fix dependencies
  • Remove obsolete py27, py34 and py35 subports

Fixes: #57789

Note: See TracTickets for help on using tickets.