On Jan 23, 2015, at 3:22 PM, Jeremy Lavergne wrote:
> Joshua pointed it out in a previous thread: we don't make use of other
> package managers (Pip in this instance), so we shouldn't have their
> packages in MacPorts unless they have requisites in MacPorts.
Ohh, I see.
Well that's not the axe
On 2015-1-24 07:22 , Jeremy Lavergne wrote:
> Joshua pointed it out in a previous thread: we don't make use of other
> package managers (Pip in this instance), so we shouldn't have their
> packages in MacPorts unless they have requisites in MacPorts.
The opposite is equally important; i.e. somethi
On Fri, Jan 23, 2015 at 2:04 PM, Lawrence Velázquez wrote:
> Close to completion. I've been meaning to send out a status update but
> haven't gotten around to it.
Great! Thanks
> New ports should only support the 2.7 and 3.4 series.
Sounds good, that'll make things much easier.
Cheers
Adam
_
>> Will your update include our stance on including all python packages
>> versus only c-modules (or otherwise needing MacPorts' involvement)?
>
> I'm not sure what you mean.
Joshua pointed it out in a previous thread: we don't make use of other
package managers (Pip in this instance), so we shoul
On Jan 23, 2015, at 3:13 PM, Jeremy Lavergne wrote:
> Will your update include our stance on including all python packages
> versus only c-modules (or otherwise needing MacPorts' involvement)?
I'm not sure what you mean.
vq
___
macports-dev mailing li
>> I recall there being an effort to cut down the number of python ports,
>> what is the status of this
>
> Close to completion. I've been meaning to send out a status update but
> haven't gotten around to it.
>
>> and what python versions are we aiming to support going forward? The
>> reason I'm a
On Jan 23, 2015, at 2:52 PM, Adam Mercer wrote:
> I recall there being an effort to cut down the number of python ports,
> what is the status of this
Close to completion. I've been meaning to send out a status update but
haven't gotten around to it.
> and what python versions are we aiming to s
Hi
I recall there being an effort to cut down the number of python ports,
what is the status of this, and what python versions are we aiming to
support going forward? The reason I'm asking is that I'm in the middle
of adding some new python variants to a port and want to make sure
that I'm not was
