I have opened a pull request to update the default version to 3.8 in the Python
PG [1].
I will also start updating my ports to 3.8 where possible.
-Marcus
[1] https://github.com/macports/macports-ports/pull/6383
> On Feb 13, 2020, at 8:30 PM, Ryan Schmidt wrote:
>
> Then the question is: why
Then the question is: why is that the default in the python portgroup?
> On Feb 6, 2020, at 09:25, Marcus Calhoun-Lopez wrote:
>
> Speaking only for myself, I have set the default Python to 3.7 in some of my
> ports even with 3.8 available because 3.7 is still the default in the python
> Port
Speaking only for myself, I have set the default Python to 3.7 in some of my
ports even with 3.8 available because 3.7 is still the default in the python
PortGroup [1].
My own rule has been: use the same version as the.PortGroup.
[1]
https://github.com/macports/macports-ports/blob/cc950d4f42c4b
> Is there a concept of "python-stable" versus "python-newest" like there is
> the -devel versions?
I don’t think so?
In my case, it turns out there were three “problematic” ports:
gobject-introspection, fonttools and libpsl. All have python 3.7 hardcoded into
their Portfile, so it’s not possi
On 2020-02-05, at 11:31 AM, Vincent wrote:
>
> In my case, I delay the bump somewhat because I know most of my ports depend
> not only on the language itself, but also on various py-xxx librairies, the
> update of which often comes pretty late after the new Python version has been
> release
Hi,
First off, I’d like to apologise for not knowing about rdeps. As I said before,
I’ve been part of the project and working on Portfiles for quite a bunch of
years, but I’m still unable to master some of the basic commands :( I’m not a
great committer.
> I suspect in most cases those commit
On Wed, 5 Feb 2020 at 19:19, Ryan Schmidt wrote:
> On Feb 5, 2020, at 11:48, Vincent Habchi wrote:
>
> > So basically I have a long list of dependents to install, one (or more) of
> > which itself/themselves depend(s) on python 3.7, at least in its/their
> > default version(s). Since I don’t want
> On 5 Feb 2020, at 6:35 pm, Ryan Schmidt wrote:
>
>
>
> On Feb 5, 2020, at 12:34, Christopher Jones wrote:
>
>> On 5 Feb 2020, at 6:19 pm, Ryan Schmidt wrote:
>>
>>> On Feb 5, 2020, at 11:48, Vincent Habchi wrote:
>>>
this time, I have another interesting quandary. When I try to inst
On Feb 5, 2020, at 12:34, Christopher Jones wrote:
> On 5 Feb 2020, at 6:19 pm, Ryan Schmidt wrote:
>
>> On Feb 5, 2020, at 11:48, Vincent Habchi wrote:
>>
>>> this time, I have another interesting quandary. When I try to install LyX,
>>> I get this message:
>>>
>>> —
>>> Air > sudo port in
> On 5 Feb 2020, at 6:19 pm, Ryan Schmidt wrote:
>
>
>
> On Feb 5, 2020, at 11:48, Vincent Habchi wrote:
>
>> this time, I have another interesting quandary. When I try to install LyX, I
>> get this message:
>>
>> —
>> Air > sudo port install LyX +python38
>> ---> Computing dependencies f
On Feb 5, 2020, at 11:48, Vincent Habchi wrote:
> this time, I have another interesting quandary. When I try to install LyX, I
> get this message:
>
> —
> Air > sudo port install LyX +python38
> ---> Computing dependencies for LyX
> The following dependencies will be installed:
> […]
> py37
On 5 Feb 2020, at 12:48, Vincent Habchi wrote:
Hi again,
this time, I have another interesting quandary. When I try to install
LyX, I get this message:
—
Air > sudo port install LyX +python38
---> Computing dependencies for LyX
The following dependencies will be installed:
[…]
py37-beaker
> port rdeps LyX
The following ports are dependencies of LyX @2.3.3_1+python27+qt5:
xz
libiconv
gperf
gettext
ncurses
bison
bison-runtime
m4
gawk
cctools
libunwind-headers
llvm-9.0
cmake
libcxx
curl
pkgconfig
lib
Hi again,
this time, I have another interesting quandary. When I try to install LyX, I
get this message:
—
Air > sudo port install LyX +python38
---> Computing dependencies for LyX
The following dependencies will be installed:
[…]
py37-beaker
py37-mako
py37-markdown
py37-markupsafe
py37-
14 matches
Mail list logo
