[Bug 204935] devel/py-icalendar: Allow building with Python 3.x (Supported since 3.6)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204935 Kubilay Kocak changed: What|Removed |Added Status|Open|In Progress -- 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 204891] [exp-run] devel/py-setuptools: update to 18.7
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204891 --- Comment #2 from commit-h...@freebsd.org --- A commit references this bug: Author: sunpoet Date: Fri Dec 4 12:35:57 UTC 2015 New revision: 402980 URL: https://svnweb.freebsd.org/changeset/ports/402980 Log: - Update to 18.7 - Use @sample - Use PLIST_FILES instead of PLIST Changes:https://pythonhosted.org/setuptools/history.html https://github.com/jaraco/setuptools/blob/master/CHANGES.txt Differential Revision:https://reviews.freebsd.org/D4307 PR:204891 Exp-run by:antoine Changes: head/devel/py-setuptools/Makefile head/devel/py-setuptools/distinfo head/devel/py-setuptools/pkg-plist -- 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 204891] devel/py-setuptools: update to 18.7
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204891 Kubilay Kocak changed: What|Removed |Added Summary|[exp-run] |devel/py-setuptools: update |devel/py-setuptools: update |to 18.7 |to 18.7 | -- 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 204891] devel/py-setuptools: update to 18.7
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204891 Kubilay Kocak changed: What|Removed |Added Flags|exp-run?|exp-run+ -- 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 204891] devel/py-setuptools: update to 18.7
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204891 --- Comment #3 from Sunpoet Po-Chuan Hsieh --- (In reply to Antoine Brodin from comment #1) devel/py-simpleparse has been updated to 2.2.0 (r402981) which builds fine with setuptools 18.7. -- 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 201385] [NEW PORT] www/py-rfc3986: Python implementation of RFC 3986
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201385 --- Comment #4 from commit-h...@freebsd.org --- A commit references this bug: Author: amdmi3 Date: Fri Dec 4 15:01:39 UTC 2015 New revision: 402991 URL: https://svnweb.freebsd.org/changeset/ports/402991 Log: A Python implementation of RFC 3986 including validation and authority parsing. WWW: https://github.com/sigmavirus24/rfc3986 PR:201385 Submitted by:y...@rawbw.com Changes: head/www/Makefile head/www/py-rfc3986/ head/www/py-rfc3986/Makefile head/www/py-rfc3986/distinfo head/www/py-rfc3986/pkg-descr -- 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 201385] [NEW PORT] www/py-rfc3986: Python implementation of RFC 3986
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201385 Dmitry Marakasov changed: What|Removed |Added Status|New |Closed Resolution|--- |FIXED Assignee|freebsd-ports-bugs@FreeBSD. |amd...@freebsd.org |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 201384] [NEW PORT] dns/py-dnschain: Python library for looking up blockchain data via DNSChain
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201384 --- Comment #9 from commit-h...@freebsd.org --- A commit references this bug: Author: amdmi3 Date: Fri Dec 4 15:03:13 UTC 2015 New revision: 402992 URL: https://svnweb.freebsd.org/changeset/ports/402992 Log: Python library for looking up blockchain data via DNSChain WWW: https://github.com/okTurtles/pydnschain PR:201384 Submitted by:y...@rawbw.com Changes: head/dns/Makefile head/dns/py-dnschain/ head/dns/py-dnschain/Makefile head/dns/py-dnschain/distinfo head/dns/py-dnschain/pkg-descr -- 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 201384] [NEW PORT] dns/py-dnschain: Python library for looking up blockchain data via DNSChain
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201384 Dmitry Marakasov changed: What|Removed |Added Resolution|--- |FIXED Assignee|freebsd-ports-bugs@FreeBSD. |amd...@freebsd.org |org | Status|New |Closed -- 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"
Python and SWIG support in ports?
Hi, I am working with the upstream maintainer of M2Crypto ( https://gitlab.com/m2crypto/m2crypto ). In the distutils that comes with Python, the swig binary is harcoded to "swig" if on a POSIX system: https://hg.python.org/cpython/file/v2.6.2/Lib/distutils/command/build_ext.py#l635 In our ports, we name our swig binaries things like "/usr/local/bin/swig2.0" or "/usr/local/bin/swig3.0". How do we deal with this in Python ports which use SWIG? If possible, I'd like to push a fix upstream for FreeBSD, if the upstream maintainer is OK with it. Thanks. -- Craig ___ 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"
Re: Python and SWIG support in ports?
On 5/12/2015 1:44 PM, Kubilay Kocak wrote: > On 5/12/2015 9:40 AM, Craig Rodrigues wrote: >> Hi, >> >> I am working with the upstream maintainer of M2Crypto ( >> https://gitlab.com/m2crypto/m2crypto ). >> >> In the distutils that comes with Python, the swig binary is harcoded >> to "swig" if on a POSIX system: >> >> https://hg.python.org/cpython/file/v2.6.2/Lib/distutils/command/build_ext.py#l635 > > Short-term, swig20 could provide a symlink to the versioned binary until > a 'more correct' and permanent fix can be made. > > I'm not sure what to do about those ports that depend on swig30 in the > presence of swig20 also being installed, given they don't appear to > CONFLICT_INSTALL on each other. They both can't provide the swig > symlink. Supporting swig in DEFAULT_VERSIONS doesn't sound right and is > probably overkill. > >> In our ports, we name our swig binaries things like >> "/usr/local/bin/swig2.0" or >> "/usr/local/bin/swig3.0". How do we deal with this in Python ports which >> use >> SWIG? > > If this is the case, it would mean all swig dependent things are also > broken. How are other ports dealing with it, or working? This might > provide some insight. > > The if os.name == "posix": branch could do the same swig > version-suffixed binary checking that the elif os.name == "nt": > condition branch does. > > A smarter way might *also* be to add functionality to that swig method > to allow the system to provide the binary path/name via envvars or > command line argument to (build,build_ext) commands explicitly. > > I suggest creating an upstream issue. By upstream I mean @ Python. >> If possible, I'd like to push a fix upstream for FreeBSD, if the upstream >> maintainer >> is OK with it. Also, another temporary workaround/option might be to implement a custom build_ext command in M2Crypto that does a smarter find_swig > Hit us up on IRC (#freebsd-python) if you'd like to talk more, or have > questions > >> Thanks. >> >> -- >> Craig > > > > ___ 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"
Re: Python and SWIG support in ports?
On 5/12/2015 9:40 AM, Craig Rodrigues wrote: > Hi, > > I am working with the upstream maintainer of M2Crypto ( > https://gitlab.com/m2crypto/m2crypto ). > > In the distutils that comes with Python, the swig binary is harcoded > to "swig" if on a POSIX system: > > https://hg.python.org/cpython/file/v2.6.2/Lib/distutils/command/build_ext.py#l635 Short-term, swig20 could provide a symlink to the versioned binary until a 'more correct' and permanent fix can be made. I'm not sure what to do about those ports that depend on swig30 in the presence of swig20 also being installed, given they don't appear to CONFLICT_INSTALL on each other. They both can't provide the swig symlink. Supporting swig in DEFAULT_VERSIONS doesn't sound right and is probably overkill. > In our ports, we name our swig binaries things like > "/usr/local/bin/swig2.0" or > "/usr/local/bin/swig3.0". How do we deal with this in Python ports which > use > SWIG? If this is the case, it would mean all swig dependent things are also broken. How are other ports dealing with it, or working? This might provide some insight. The if os.name == "posix": branch could do the same swig version-suffixed binary checking that the elif os.name == "nt": condition branch does. A smarter way might *also* be to add functionality to that swig method to allow the system to provide the binary path/name via envvars or command line argument to (build,build_ext) commands explicitly. I suggest creating an upstream issue. > If possible, I'd like to push a fix upstream for FreeBSD, if the upstream > maintainer > is OK with it. Hit us up on IRC (#freebsd-python) if you'd like to talk more, or have questions > Thanks. > > -- > Craig ___ 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"
