[Bug 221238] mail/py-authres: Update to 1.0.1

2017-08-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221238

Kubilay Kocak  changed:

   What|Removed |Added

 Status|New |Open
   Keywords||easy
 CC||pyt...@freebsd.org

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-python@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-python
To unsubscribe, send any mail to "freebsd-python-unsubscr...@freebsd.org"


[Bug 213636] math/py-matplotlib: Fails to build with python3

2017-08-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213636

--- Comment #11 from Kubilay Kocak  ---
To explicitly separate the issues here:

1) Does matplotlib 1.5.3 support (bugs and build environments aside) Python
3.x? If so, USES=python: should reflect that (upstream intended)
version support as closely as possible without being incorrect.

2) Does this ports OPTIONS_DEFAULT (or its dependencies OPTIONS_DEFAULT),
support building with both Python 2 and 3. If so, there's nothing to do. If
not, OPTIONS_DEFAULTS should change to make that the case.

3) If (2) results in changes, what impacts does this have and what other
changes may be required in other ports/packages. There could be conflicting
dependencies from other ports and/or their dependencies, users could be forced
to run multiple frontend frameworks, etc.

(1) can and should be resolved independently from (2) potentially (3)

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-python@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-python
To unsubscribe, send any mail to "freebsd-python-unsubscr...@freebsd.org"


[Bug 213636] math/py-matplotlib: Fails to build with python3

2017-08-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213636

--- Comment #10 from Kubilay Kocak  ---
(In reply to rsmith from comment #9)

The word 'work' was specifically and intentionally not used, to focus just on
whether or not the USES=python: is incorrect as it relates to
what matplotlib is supposed to support (per upstream), not whether other
factors (default options or other issues/bugs) prevent that from being true at
a certain point in time or in certain conditions (downstream).

Keep in mind that USES=python: is a declarative specifier (port
supports this/these versions), not an imperative one (use this version)

Looking back, ports r426883 (update to 1.5.3) states:

- Additionally, 1.5.3 version doesn't build with python-3.X because
  'import gtk' which the build tries fails in python3. Therefore, python:2.

Based on this and on my reading of this issue (which may be incorrect or
incomplete), this was and is an incorrect (at a minimum, imprecise) warrant
and/or method for restricting builds to 2.7.

1) If the presence (or non-presence) or a build configuration (OPTION or
OPTIONs in this case) prevents building with a particular version, then the
restriction should be limited/scoped to that build option or build options, not
globally.

2) If a python package ('upstream python package' is meant here, not 'freebsd
package') supports Python 2 and 3 builds, then the default configuration (read:
OPTIONS_DEFAULTS) of the port and it's dependencies should support building
with 2/3 by default.

Accordingly, and at a minimum:

1) USES=python: should be relaxed and be made to correctly
reflect that matplotlib supports both Python 2 & 3. 

2) The OPTIONS_DEFAULTS of this port should be modified to work with Python 2
and 3 builds (if that is indeed possible).

(1) and (2) alone are probably insufficient to ensure a good user experience,
if certain combinations of OPTIONS must be enabled/disabled to produce a valid
Python 3 build environment, so:

If certain options are mutually exclusive (in that some prevent Python 2 or 3
builds), then OPTIONS_RADIO's or conditional blocks should be added that check
for valid/invalid options combinations and inform the user with appropriate
BROKEN/IGNORE/other methods when incompatible options/configurations are
selected.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-python@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-python
To unsubscribe, send any mail to "freebsd-python-unsubscr...@freebsd.org"


FreeBSD ports you maintain which are out of date

2017-08-04 Thread portscout
Dear port maintainer,

The portscout new distfile checker has detected that one or more of your
ports appears to be out of date. Please take the opportunity to check
each of the ports listed below, and if possible and appropriate,
submit/commit an update. If any ports have already been updated, you can
safely ignore the entry.

You will not be e-mailed again for any of the port/version combinations
below.

Full details can be found at the following URL:
http://portscout.freebsd.org/pyt...@freebsd.org.html


Port| Current version | New version
+-+
textproc/py3-docutils   | 0.13.1  | 0.14
+-+
www/xist| 5.28.1  | 5.28.2
+-+


If any of the above results are invalid, please check the following page
for details on how to improve portscout's detection and selection of
distfiles on a per-port basis:

http://portscout.freebsd.org/info/portscout-portconfig.txt

Thanks.
___
freebsd-python@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-python
To unsubscribe, send any mail to "freebsd-python-unsubscr...@freebsd.org"