Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Billiard 2.7.3.10 issues with bytes / strings #11

Closed
humbuckler opened this issue Jul 25, 2012 · 0 comments
Closed

Billiard 2.7.3.10 issues with bytes / strings #11

humbuckler opened this issue Jul 25, 2012 · 0 comments

Comments

@humbuckler
Copy link

Trying to run billiard 2.7.3.10 with Celery in Python 3.2. I get the following error (suggested fix below):
[2012-07-25 10:29:27,504: ERROR/MainProcess] Unrecoverable error: TypeError('string argument without an encoding',)
Traceback (most recent call last):
File "/usr/local/lib/python3.2/dist-packages/celery-3.0.3-py3.2.egg/celery/worker/init.py", line 350, in start
component.start()
File "/usr/local/lib/python3.2/dist-packages/celery-3.0.3-py3.2.egg/celery/concurrency/base.py", line 109, in start
self.on_start()
File "/usr/local/lib/python3.2/dist-packages/celery-3.0.3-py3.2.egg/celery/concurrency/processes/init.py", line 84, in on_start
**self.options)
File "/usr/local/lib/python3.2/dist-packages/billiard-2.7.3.10-py3.2.egg/billiard/pool.py", line 760, in init
self._setup_queues()
File "/usr/local/lib/python3.2/dist-packages/billiard-2.7.3.10-py3.2.egg/billiard/pool.py", line 990, in _setup_queues
self._inqueue = SimpleQueue()
File "/usr/local/lib/python3.2/dist-packages/billiard-2.7.3.10-py3.2.egg/billiard/queues.py", line 339, in init
self._reader, self._writer = Pipe(duplex=False)
File "/usr/local/lib/python3.2/dist-packages/billiard-2.7.3.10-py3.2.egg/billiard/init.py", line 113, in Pipe
from .connection import Pipe
File "/usr/local/lib/python3.2/dist-packages/billiard-2.7.3.10-py3.2.egg/billiard/connection.py", line 426, in
CHALLENGE = bytes('#CHALLENGE#')
TypeError: string argument without an encoding

By specifying an encoding in lines 426-428 of connection.py, it got past this error. Not sure if other things will pop up elsewhere, however.

other options might be utf_32, utf_16

CHALLENGE = bytes('#CHALLENGE#','ascii')

WELCOME = bytes('#WELCOME#','ascii')

FAILURE = bytes('#FAILURE#','ascii')

@ask ask closed this as completed in 4efdbe6 Jul 30, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants