Page MenuHomeFreeBSD

Use python 2.7+ instead of 3.6 in mail/claws-mail

Authored by joneum on Jan 10 2019, 10:34 AM.



After r489852, i talk with koobs on irc.
He suggested using python better: 2.7+. So the user can decide he wants Python 2.7 or higher.
I think that's a very good idea.
I open this review to discuss this with mmokhi as well.
This review is for the change from 3.6 to 2.7+. The poudrire tests look good:

koobs also suggested to use "dm" instead of "m" in the patch. There is an error here:

I am not sure: when changing the Python version, does PORTREVISION need to be bump?

Diff Detail

rP FreeBSD ports repository
No Linters Available
No Unit Test Coverage
Build Status
Buildable 21911
Build 21155: arc lint + arc unit

Event Timeline

joneum created this revision.Jan 10 2019, 10:34 AM
mmokhi updated this revision to Diff 52729.Jan 10 2019, 11:51 AM

About python27 compatibility I think it's good idea definitely
(It's good that you tested it and it's fine too ๐Ÿ˜Š I think the changes on the previous commit were mostly compatible).

For the m/dm stuff, I'm actually not very sure what @koobs meant, but
I propose this change (which tested and seems working for me),
so if you both can verify I appreciate ๐Ÿ˜„
I thinks it covers now all python versions (and all m/dm/blanks).

Oh and about the PORT_REVISION I support changing it, because we're making change on of claws-mail
So sub-ports should get notified. It's safer decision imho :)

linimon retitled this revision from Use python 2.7+ instead of 3.6 in claws-mail to Use python 2.7+ instead of 3.6 in mail/claws-mail.Jan 11 2019, 12:23 AM
koobs accepted this revision.EditedJan 12 2019, 2:06 AM

It's not that 2.7+ is "better", its that :3.6 is "incorrect" in that:

  • It forces one specific version unnecessarily
  • It doesn't accurately/precisely describe the versions the software does supports (basically: any version)

The pattern/guidelines is:

  • The Python ports version specifier should be the set of Python versions that the package supports, not what Python version should be used (declarative vs imperative). Unfortunately the distinction is made more difficult to grok because of the name of the USES directive, which has an imperative meaning.

What this means in practice is:

  • Don't specify one version unless the package *only* supports that (and only that) one specific version. There are practically no python packages in the world that are like this. For python "ports".

Also, please make sure this gets to quarterly too (MFH)

This revision is now accepted and ready to land.Jan 12 2019, 2:06 AM
joneum closed this revision.Jun 11 2019, 4:23 PM