On Thu, Nov 30, 2017 at 11:34:59AM -0500, Daniel Jakots wrote: > On Thu, 30 Nov 2017 17:19:59 +0100, Klemens Nanni <k...@posteo.org> wrote: > > > However I purposefully wrote aggregate6 in such a way that it can > > > work in both python2 and python3 environments to enable broader > > > applicability. > > > > Fair point with regards to portability but not when it comes to new > > ports. These are just my to cents, I'm happy to hear from others. > > > > Attached is a diff on top of your tarball to ship it as Python 3 only, > > only lightly tested. > > I agree for ports that are only utilities written in python but I > disagree when it comes to library and Job said in his initial mail that > it can also be used as a library.
I really wouldn't mind adding this as a python3-only port. I (as upstream) added python2 compatibility as an afterthought anyway. The advantage of treating this 'python3 only' is that the 'aggregate6' cli tool can then point to the python3 interpreter (which performs better compared to running aggregate6 in python2) and be called 'aggregate6' instead of 'aggregate6-3'. If people really need the library aspect of the aggregate6 tool, in python2, on openbsd, they could consider using pip inside a virtualenv, which they'll probaly be doing anyway. Feedback welcome, i am a novice to openbsd ports. Kind regards, Job
