[Bug 168159] Mk/bsd.python.mk: CMake python detection gets confused if multiple python versions are installed

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=168159 --- Comment #15 from commit-h...@freebsd.org --- A commit references this bug: Author: makc Date: Wed Jun 10 09:23:54 UTC 2015 New revision: 389024 URL: https://svnweb.freebsd.org/changeset/ports/389024 Log: Pass the default Python versi

[Bug 168159] Mk/bsd.python.mk: CMake python detection gets confused if multiple python versions are installed

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=168159 Max Brazhnikov changed: What|Removed |Added Status|Open|Closed Resolution|---

[Bug 200518] games/golly: Force CMake to use python27 (and ignore python34)

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200518 Bug 200518 depends on bug 168159, which changed state. Bug 168159 Summary: Mk/bsd.python.mk: CMake python detection gets confused if multiple python versions are installed https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=168159

Python Subprocess Crontab Problem

I'm running into a wall with regards to using subprocess.call in a python script running in a crontab. I have isolated this problem to be subprocess not able to find the 7z executable. I have tried adding PYTHONPATH=$PATH to crontab, I have tried adding shell=True to subprocess.call, and I have tri

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

Re: Python Subprocess Crontab Problem

On Wed, Jun 10, 2015 at 5:02 PM, Craig Rodrigues wrote: > Can you add right here: >print("PATH: %s" % os.environ['PATH'], file=errors) > > and see what the PATH is in your errors file? I should have mentioned that I'm using python3. The above is causing a TypeError: TypeError: 'str' does

Re: Re: Python Subprocess Crontab Problem

crontab isn't using a PATH for your specified user, so you need to give an absolute path. On Wed, 10 Jun 2015 14:02:06 -0700 Craig Rodrigues wrote On Wed, Jun 10 > Here is how I'm calling the script in crontab: > PATH=$PATH:/usr/local/bin > I can't remem

Re: Re: Python Subprocess Crontab Problem

On Wed, Jun 10, 2015 at 5:33 PM, Chris Wojo wrote: > crontab isn't using a PATH for your specified user, so you need to give an > absolute path. This is the fix. Thanks everyone! ___ freebsd-python@freebsd.org mailing list http://lists.freebsd.org/mailm

[Bug 199138] [NEW PORT] devel/py-cov-core: Plugin core for use by pytest-cov, nose-cov and nose2-cov

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199138 Kubilay Kocak changed: What|Removed |Added Attachment #155149||maintainer-approval+

[Bug 199138] [NEW PORT] devel/py-cov-core: Plugin core for use by pytest-cov, nose-cov and nose2-cov

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199138 Kubilay Kocak changed: What|Removed |Added Keywords|needs-qa|patch-ready --- Comment #3 from Ku