Opened 14 years ago

Last modified 5 years ago

#26184 new request

py-file: File python module

Reported by: hsivank@… Owned by: macports-tickets@…
Priority: Normal Milestone:
Component: ports Version:
Keywords: Cc: ryandesign (Ryan Carsten Schmidt), petrrr, chrstphrchvz (Christopher Chavez)
Port: py-file file

Description

File integrates a python module. Currently it is not build.

Change History (11)

comment:1 Changed 14 years ago by hsivank@…

Cc: hsivank@… added

Cc Me!

comment:2 Changed 14 years ago by jmroot (Joshua Root)

Cc: jay-macports@… hsivank@… removed
Owner: changed from macports-tickets@… to jay-macports@…
Version: 1.9.1

comment:3 Changed 13 years ago by ryandesign (Ryan Carsten Schmidt)

Owner: changed from jay-macports@… to macports-tickets@…

If we were to build a python module, it would be in a separate py-file port, not in the file port.

comment:4 Changed 10 years ago by petrrr

Cc: Peter.Danecek@… added

Cc Me!

comment:5 Changed 9 years ago by petrrr

Port: py-file added
Summary: File python modulepy-file: File python module
Type: enhancementrequest

comment:6 Changed 9 years ago by jmroot (Joshua Root)

Cc: ryandesign@… added

comment:7 Changed 9 years ago by petrrr

Cc: petr@… added

Cc Me!

comment:8 Changed 8 years ago by petrrr

Cc: Peter.Danecek@… removed

comment:9 Changed 8 years ago by petrrr

I am a bit puzzled what to do with this old ticket.

The situation today seems to be that there are several Python packages offering similar functionality. They all use the same top level name magic. Here an overview:

  • This ticket request for the wrapper module provided by file itself, see [1].
  • Macports already provides a package called python-magic as port py-magic. References [2] and [3]
  • ... and there is filemagic [4], [5] (not maintained)

filemagic is probably now irrelevant anyway. This ticket was not implemented in years, it would create a conflict with the existing port and the existing port has dependencies. This indicates that the file implementation is less popular. I'd propose to close this ticket as wontfix and consider implementing it only if it should be required as dependency.

References:

Last edited 8 years ago by ryandesign (Ryan Carsten Schmidt) (previous) (diff)

comment:10 Changed 5 years ago by chrstphrchvz (Christopher Chavez)

Can this be closed as wontfix, or is some other approach preferable?

comment:11 Changed 5 years ago by chrstphrchvz (Christopher Chavez)

Cc: chrstphrchvz added
Note: See TracTickets for help on using tickets.