generate_will_project aborts on osx 10.9.2

[kowsik]

Trying to use will on a project and running generate_will_project on osx 10.9.2 causes this exception:

Traceback (most recent call last):
  File "/usr/local/bin/generate_will_project", line 5, in <module>
    from pkg_resources import load_entry_point
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/Extras/lib/python/pkg_resources.py", line 2603, in <module>
    working_set.require(__requires__)
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/Extras/lib/python/pkg_resources.py", line 666, in require
    needed = self.resolve(parse_requirements(requirements))
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/Extras/lib/python/pkg_resources.py", line 565, in resolve
    raise DistributionNotFound(req)  # XXX put more info here
pkg_resources.DistributionNotFound: apscheduler

Any ideas what's going on? pip install got me will (0.4.2).

[skoczen]

Yep - this is pip complaining about not being able to get apscheduler.

As for why you're seeing that, I'm less clear on that. Are you behind any funky proxies or the like?

Here's what I get, pip installing apscheduler - I'd say run generate_will_project again, and if that fails, try the below, and paste your results.

[ skoczen Chinook ~ ] 
$ mkvirtualenv test
New python executable in test/bin/python2.7
Also creating executable in test/bin/python
Installing Setuptools...............................................................................................................................................................................................p...............................done.
Installing Pip.....................................................................................................................................................................................................................................................................................................................................done.
(test)[ skoczen Chinook ~ ] 
$ pip install apscheduler
Downloading/unpacking apscheduler
  Downloading APScheduler-2.1.2.tar.gz (41kB): 41kB downloaded
  Running setup.py egg_info for package apscheduler

Installing collected packages: apscheduler
  Running setup.py install for apscheduler

Successfully installed apscheduler
Cleaning up...
(test)[ skoczen Chinook ~ ] 

[kowsik]

Hmm, running inside virtualenv fixed the problem. Must've been some global conflict. Thanks for the quick response.

[skoczen]

Yup - and I'd bet it was a quick downtime/DNS issue on pypi more than your system, if I were a betting man. Glad it's working!

[kowsik]

Somewhat related, what do I set the WILL_USERNAME/WILL_PASSWORD to be for
the bot? Is it the same as the Jabber ID / account password on Hipchat or
something else?

On Thu, Mar 13, 2014 at 2:28 PM, Steven Skoczen notifications@github.comwrote:

Yup - and I'd bet it was a quick downtime/DNS issue on pypi more than your
system, if I were a betting man. Glad it's working!

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/9#issuecomment-37589171
.

[skoczen]

Yep, username is the jabber id (12345_123456@chat.hipchat.com), password is that user's password on hipchat.

Someday, I'd like to just use the v2 token, and skip all that, but for the moment, the APIs aren't feature complete enough to do everything will needs.

[kowsik]

Hopefully one last question! :) I think I have everything configured and
there are no error messages, but the bot doesn't actually join and show up
in the room. Do you know or have any pointers on debugging this?

I added a couple of print statements to see what's going on:

will/listener.py#join_rooms does print out the rooms
sleekxmpp/plugins/xep_0045.py#joinMUC does seem to announce the presence

A bit of a loss as to how else I can debug this.

Thanks Steven!

K.

On Thu, Mar 13, 2014 at 3:02 PM, Steven Skoczen notifications@github.comwrote:

Yep, username is the jabber id (12345_123456@chat.hipchat.com), password
is that user's password on hipchat.

Someday, I'd like to just use the v2 token, and skip all that, but for the
moment, the APIs aren't feature complete enough to do everything will needs.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/9#issuecomment-37592478
.

[kowsik]

Okay, figured it out (you might want to doc this).

The WILL_NAME needs to be exactly what's configured inside Hipchat. In
run_will.py, I added these lines:

import logging.config
logging.basicConfig(level=logging.DEBUG)

to figure out what went wrong.

Thanks for this project though. Looks pretty fun, now that I have it
working!

On Thu, Mar 13, 2014 at 8:43 PM, kowsik kowsik@gmail.com wrote:

Hopefully one last question! :) I think I have everything configured and
there are no error messages, but the bot doesn't actually join and show up
in the room. Do you know or have any pointers on debugging this?

I added a couple of print statements to see what's going on:

will/listener.py#join_rooms does print out the rooms
sleekxmpp/plugins/xep_0045.py#joinMUC does seem to announce the presence

A bit of a loss as to how else I can debug this.

Thanks Steven!

K.

On Thu, Mar 13, 2014 at 3:02 PM, Steven Skoczen notifications@github.comwrote:

Yep, username is the jabber id (12345_123456@chat.hipchat.com), password
is that user's password on hipchat.

Someday, I'd like to just use the v2 token, and skip all that, but for
the moment, the APIs aren't feature complete enough to do everything will
needs.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/9#issuecomment-37592478
.

[skoczen]

Ah, yep, that's one of those knowns that's evidently just in my head - putting it in the docs!