Issue on upgrading to 0.1.13

[hotmeteor]

Getting an error trying to run lemonsync after upgrading to 0.1.13:

Traceback (most recent call last):
  File "/usr/local/bin/lemonsync", 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: boto>=2.27.0

[ChrisZieba]

Did you get an error when upgrading? I noticed that the last pip package was named incorrectly, which is now fixed. That may have caused the upgrade to fail without you noticing, and now one of the dependencies is not installed.

[hotmeteor]

I just uninstalled it and reinstalled it, and it looked fine:

Downloading/unpacking lemonsync
  Downloading lemonsync-0.1.14.tar.gz
  Running setup.py (path:/private/tmp/pip_build_root/lemonsync/setup.py) egg_info for package lemonsync

Requirement already satisfied (use --upgrade to upgrade): watchdog>=0.7.1 in /Library/Python/2.7/site-packages/watchdog-0.7.1-py2.7-macosx-10.9-intel.egg (from lemonsync)
Requirement already satisfied (use --upgrade to upgrade): requests>=2.2.1 in /Library/Python/2.7/site-packages/requests-2.3.0-py2.7.egg (from lemonsync)
Requirement already satisfied (use --upgrade to upgrade): boto>=2.27.0 in /Library/Python/2.7/site-packages (from lemonsync)
Requirement already satisfied (use --upgrade to upgrade): colorama>=0.3.1 in /Library/Python/2.7/site-packages (from lemonsync)
Requirement already satisfied (use --upgrade to upgrade): pathtools>=0.1.1 in /Library/Python/2.7/site-packages/pathtools-0.1.2-py2.7.egg (from lemonsync)
Requirement already satisfied (use --upgrade to upgrade): PyYAML>=3.09 in /Library/Python/2.7/site-packages/PyYAML-3.11-py2.7-macosx-10.9-intel.egg (from watchdog>=0.7.1->lemonsync)
Requirement already satisfied (use --upgrade to upgrade): argh>=0.8.1 in /Library/Python/2.7/site-packages/argh-0.24.1-py2.7.egg (from watchdog>=0.7.1->lemonsync)
Installing collected packages: lemonsync
  Running setup.py install for lemonsync

    Installing lemonsync script to /usr/local/bin
Successfully installed lemonsync
Cleaning up...

However, still getting the same error when trying to run.

[ChrisZieba]

Looks like the dependencies are not getting installed. What versions of Mac OS, Xcode, and pip are installed?

[hotmeteor]

OS X 10.9.2 Xcode 5.1.1 pip 1.5.6

[ChrisZieba]

There have been some issues compiling some of the dependencies on 10.9.x with Xcode 5.1. Can you try installing lemonsync with the additional compiler flags noted here: https://github.com/lemonstand/lemonsync/wiki/Installation

[hotmeteor]

Ok, re-ran it with the flag, but still no dice:

sudo ARCHFLAGS=-Wno-error=unused-command-line-argument-hard-error-in-future pip install lemonsync

Downloading/unpacking lemonsync
  Downloading lemonsync-0.1.14.tar.gz
  Running setup.py (path:/private/tmp/pip_build_root/lemonsync/setup.py) egg_info for package lemonsync

Requirement already satisfied (use --upgrade to upgrade): watchdog>=0.7.1 in /Library/Python/2.7/site-packages/watchdog-0.7.1-py2.7-macosx-10.9-intel.egg (from lemonsync)
Requirement already satisfied (use --upgrade to upgrade): requests>=2.2.1 in /Library/Python/2.7/site-packages/requests-2.3.0-py2.7.egg (from lemonsync)
Requirement already satisfied (use --upgrade to upgrade): boto>=2.27.0 in /Library/Python/2.7/site-packages (from lemonsync)
Requirement already satisfied (use --upgrade to upgrade): colorama>=0.3.1 in /Library/Python/2.7/site-packages (from lemonsync)
Requirement already satisfied (use --upgrade to upgrade): pathtools>=0.1.1 in /Library/Python/2.7/site-packages/pathtools-0.1.2-py2.7.egg (from lemonsync)
Requirement already satisfied (use --upgrade to upgrade): PyYAML>=3.09 in /Library/Python/2.7/site-packages/PyYAML-3.11-py2.7-macosx-10.9-intel.egg (from watchdog>=0.7.1->lemonsync)
Requirement already satisfied (use --upgrade to upgrade): argh>=0.8.1 in /Library/Python/2.7/site-packages/argh-0.24.1-py2.7.egg (from watchdog>=0.7.1->lemonsync)
Installing collected packages: lemonsync
  Running setup.py install for lemonsync

    Installing lemonsync script to /usr/local/bin
Successfully installed lemonsync
Cleaning up...

[hotmeteor]

I've got it to work by going into /Library/Python/2.7/site-packages/lemonsync-0.1.14-py2.7.egg-info/requires.txt and commenting out the boto line. But that seems like it's not ideal.

[ChrisZieba]

Can you try removing boto, pip uninstall boto and reinstalling lemonsync

[hotmeteor]

Did that, boto installs fine, still won't sync. Same error.

[ChrisZieba]

I think lemonsync is looking for version 2.27 of boto. I will double check this.

[hotmeteor]

Any resolution for this? I have 0.1.14 and it still doesn't work.

[ChrisZieba]

Can you try completely uninstalling lemonsync, as well as boto, and then installing v0.1.15.

[ChrisZieba]

Also, is this in a virtualenv?

[hotmeteor]

Ok, I got it to work in a virtualenv. However, originally I had it working without one. Is it necessary to use a virtualenv for each theme?

Sorry, not super familiar with python's inner workings.

[ChrisZieba]

This should work without the need of a virtualenv. It looks like pip installed system packages somewhere other than /System/Library/Frameworks/Python.framework/Versions/2.7/Extras/. If I had to guess boto is most likely installed in /Library/Python/2.7/site-packages. Not sure why it worked up until v0.1.14, could have been due to a system upgrade.

What is the output of which python?

[hotmeteor]

which python results in /usr/bin/python

Yes, both lemonstand and boto are installed in /Library/Python/2.7/site-packages, I don't think pip has put anything into /System/Library/Frameworks/Python.framework/Versions/2.7/Extras/.

[hotmeteor]

I believe this is resolved now. I cleared a bunch of crap out and tried again and all seems well. Thanks.