py-libvirt problems with bhyve

Hi, I did the following: (1) Set up libvirt, taking Roman's latest port, and configuring bhyve support: http://people.freebsd.org/~rodrigc/libvirt/libvirt-bhyve.html (2) Installed the py-libvirt port. I wrote this code: import libvirt import sys conn = libvirt.openReadOnly(None) if

Re: py-libvirt problems with bhyve

On Wed, Jun 25, 2014 at 11:01 AM, Roman Bogorodskiy wrote: > Craig Rodrigues wrote: > > > > > conn = libvirt.openReadOnly(None) > ^^^ > > I think here the URI should be 'bhyve:///system'. > Or you could tweak libvirt.co

Call for Help: Flame Graphs and Continuous Integration

FYI: https://lists.freebsd.org/pipermail/freebsd-testing/2014-November/000667.html Please send follow-ups to freebsd-test...@freebsd.org -- Craig ___ freebsd-python@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-python To un

Call for Help: Setting up Saltstack for devops of jenkins.freebsd.org cluster

FYI, https://lists.freebsd.org/pipermail/freebsd-testing/2014-December/000693.html Please send follow-ups to freebsd-test...@freebsd.org . Thanks. -- Craig -- Craig ___ freebsd-python@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo

ctypes problem loading libc.so on FreeBSD current

Hi, I am looking at this blog post for loading libc with ctypes: http://blogs.freebsdish.org/rpaulo/2008/11/30/sysctlbyname3-and-others-from-python/ I am using this version of python from ports: Name : python Version: 2.7_2,2 Installed on : Mon Jan 12 22:10:27 PST 2015 Orig

Re: ctypes problem loading libc.so on FreeBSD current

On Thu, Feb 12, 2015 at 11:42 PM, Marcus von Appen wrote: > > You described the problem above. ctypes is unable to load linker > scripts. The general advise is to use find_library(): > > >>> import ctypes > >>> import ctypes.util > >>> clib = ctypes.util.find_library("c") > >>> print clib > libc.

Re: Python Subprocess Crontab Problem

On Wed, Jun 10 > Here is how I'm calling the script in crontab: > PATH=$PATH:/usr/local/bin > I can't remember offhand, but I don't think you can do that. I think you may need to fully specify the PATH instead of using $PATH. > errors = open('/home/myuser/error', 'wb') > > with tempfile.Tempor

Python3, ImportError: No module named '_sqlite3'

Hi, I did the following on a FreeBSD 10.2 system: pkg install lang/python35 python3.5 -c "import sqlite3" and got this error: Traceback (most recent call last): File "", line 1, in ImportError: No module named 'sqlite' [rodrigc@rodrigc-laptop1 portingdb]% python3.5 -c "import sqlite3" Trace

Re: Python3, ImportError: No module named '_sqlite3'

On Sat, Nov 14, 2015 at 7:28 AM, Volodymyr Kostyrko wrote: > On 14.11.2015 17:18, Craig Rodrigues wrote: > >> Hi, >> >> I did the following on a FreeBSD 10.2 system: >> >> pkg install lang/python35 >> >> python3.5 -c "import sqlite3" &

Re: Python curses module does not print any attributed space character on FreeBSD 11-current

On Wed, Nov 18, 2015 at 7:51 PM, raviqqe wrote: > Hello, > > TL;DR > I encountered a bug-like behavior of a Python built-in module. > Could you reproduce it in C? > > While working with Python and its curses module on FreeBSD 11-current > (x86_64), > I found a weird behavior of the module. The co

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

Re: Python and SWIG support in ports?

On Fri, Dec 4, 2015 at 2:40 PM, 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

Re: Python and SWIG support in ports?

On Fri, Dec 4, 2015 at 6: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 w

Re: Python and SWIG support in ports?

On Tue, Dec 8, 2015 at 4:09 PM, Kubilay Kocak wrote: > The correct thing to do is be PEP-394'ish compatible (even though swig > itself isnt a python package). Again swig20 is a short term solution. > > I have no idea why you refered to PEP394. > The root cause is technically an inadequate 'fin

[Differential] D10162: Summary: Change to buildbot 0.9.5

rodrigc added a reviewer: freebsd-python-list. REPOSITORY rP FreeBSD ports repository REVISION DETAIL https://reviews.freebsd.org/D10162 EMAIL PREFERENCES https://reviews.freebsd.org/settings/panel/emailpreferences/ To: rodrigc, grembo, freebsd-python-list Cc: mat

[Differential] [Commented On] D2600: [new port] devel/py-pytest-timeout

rodrigc added a subscriber: rodrigc. rodrigc added a comment. @loader: even if you do not have a ports commit bit, you are allowed to commit to ports if you put **Approved by:** a ports committer in your commit message. See: https://www.freebsd.org/doc/en_US.ISO8859-1/articles/committers-guide/ar