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
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
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
setuptools has been updated quite a few times recently upstream
(version 17.0 as of Friday). Is there a dependency that is holding our
port at version 5.5.1?
___
freebsd-python@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-pyt
I'm getting an error on install of the databases/py-sqlite3:
===> Installing for py34-sqlite3-3.4.3_6
===> Checking if py34-sqlite3 already installed
===> Registering installation for py34-sqlite3-3.4.3_6
pkg-static: Plist error, directory listed as a file:
lib/python3.4/lib-dynload/_sqlite3-0
I appreciate the assistance. Setting the LANG variable does the trick.
I made the change system-wide by adding the following to
/etc/login.conf
LC_COLLATE=C
charset=UTF-8
lang=en_US.UTF-8
Now the output is correct:
>>> b'\xc3\xa2'.decode('utf-8')
'รข'
>>> import sys
>>> print(sys.stdout.encoding)
U
What is the output from print(sys.stdout.encoding) on your system?
And, can you explain how to change that on mine so that it is UTF-8?
Mine is a default fresh install, btw.
On Thu, Jan 29, 2015 at 2:29 AM, Roland Smith wrote:
> On Thu, Jan 29, 2015 at 01:38:21AM -0500, Robert Simmons wr
out.encoding)
UTF-8
How do I modify stdout encoding to set it to UTF-8 in FreeBSD?
On Thu, Jan 29, 2015 at 1:38 AM, Robert Simmons wrote:
> I'm having a unicode problem on FreeBSD lang/python34 that does not
> appear on MacOS X. I've condensed the problem to one single line to
&g
I'm having a unicode problem on FreeBSD lang/python34 that does not
appear on MacOS X. I've condensed the problem to one single line to
enter in the interpreter:
FreeBSD:
Python 3.4.2 (default, Jan 28 2015, 22:23:57)
[GCC 4.2.1 Compatible FreeBSD Clang 3.4.1 (tags/RELEASE_34/dot1-final
208032)] on
I think the best option is A&C: to remove libffi from python and to
update our port. The config choice itself can then be removed from the
python port.
On Thu, Dec 25, 2014 at 11:37 PM, Kubilay Kocak wrote:
> On 26/12/2014 3:06 PM, Robert Simmons wrote:
>> The default for lang/pytho
Beautiful Soup 3.x is Python 2.x only. From the website:
"Beautiful Soup 3 works only under Python 2.x."
http://www.crummy.com/software/BeautifulSoup/
On Sun, Jul 6, 2014 at 3:56 PM, Melvyn Sopacua wrote:
> Hello,
>
> I'm coming accross a few ports that are in the tree as we speak, that do
> not
Is there an ETA for updating the python27 port to 2.7.7?
___
freebsd-python@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-python
To unsubscribe, send any mail to "freebsd-python-unsubscr...@freebsd.org"
Is there an ETA for updating the python27 port to 2.7.7?
___
freebsd-python@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-python
To unsubscribe, send any mail to "freebsd-python-unsubscr...@freebsd.org"
Ports tree updated, but it is still a problem. I don't see anything
that was checked in recently that mentions this problem.
On Sun, Mar 3, 2013 at 1:10 AM, Martin Wilke wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Sun, Mar 03, 2013 at 12:08:41AM -0500, Rob
Sorry, what was the change you made?
On Sun, Mar 3, 2013 at 1:10 AM, Martin Wilke wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Sun, Mar 03, 2013 at 12:08:41AM -0500, Robert Simmons wrote:
>> It looks like a port revision made a few hours ago has broken fi
It looks like a port revision made a few hours ago has broken firefox
(and most likely a bunch of other ports). In the makefile for
firefox, it has the following checks for dependencies:
BUILD_DEPENDS= nspr>=4.9.4:${PORTSDIR}/devel/nspr \
nss>=3.14.1:${PORTSDIR}/security/nss \
16 matches
Mail list logo
