Packaging a Python module

[Joshua Root]

Yes. If you want to use a Portfile with subports that isn't in an 
indexed location listed in sources.conf, you have to both specify which 
Portfile to use and which subport you want, e.g.:

port info current subport=py311-fmf

The 'current' pseudoport looks in the current working directory and is 
also the default used when you don't otherwise specify any port to 
operate on. You could also specify a Portfile using a porturl.

- Josh

On 19/7/2024 02:09, Link Dupont via macports-dev wrote:
> So do I have to have the dports directory generated by pypi2port in my sources.conf in order for them to be detected?
> 
>> On Jul 18, 2024, at 10:57, Renee Otten <ottenr.work at gmail.com> wrote:
>>
>> I would recommend trying to use the “upt” package (available in MacPorts) to generate Python portfiles, but “pypi2port” should work as well.
>>
>> The most likely reason that it doesn't find the port you just added is that you did not run “portindex”.
>>
>> Best,
>> Renee
>>
>>> On Jul 18, 2024, at 10:39 AM, Link Dupont via macports-dev <macports-dev at lists.macports.org> wrote:
>>>
>>> Hello,
>>>
>>> I’m trying to package a Python module. I found the port pypi2port, which does generate a basic Portfile for me, but when I try to build the port, it gives me a puzzling error:
>>>
>>>> --->  Computing dependencies for py-fmf
>>>> Error: Dependency 'py311-fmf' not found.