On Pinax trunk: python-twitter==0.6 dependency cannot be satisfied currently

18 views

Skip to first unread message

limist

unread,

Feb 15, 2011, 12:01:23 PM2/15/11

to pinax...@googlegroups.com

With the current (checked out today, Feb.15) Pinax trunk, the requirements/pinax.txt file lists python-twitter==0.6 as a requirement, but PyPI only has 0.5, so a pip install of requirements fails unless that dependency line is commented out. The project homepage at http://code.google.com/p/python-twitter/ shows they're now up to 0.8.1 anyway.

Also, I did a quick search of the codebase and am not sure python-twitter is actually in use. If it really is, can someone point out where?

More importantly, given the fresh-start branch and such, where should bugs be reported? Maybe I'll get slapped for saying this, but why not use github's issue tracking? :) Thanks.

Brian Rosner

unread,

Feb 15, 2011, 7:23:51 PM2/15/11

to pinax...@googlegroups.com

On Tue, Feb 15, 2011 at 10:01 AM, limist <k...@limist.com> wrote:
> With the current (checked out today, Feb.15) Pinax trunk, the
> requirements/pinax.txt file lists python-twitter==0.6 as a requirement, but
> PyPI only has 0.5, so a pip install of requirements fails unless that
> dependency line is commented out. The project homepage
> at http://code.google.com/p/python-twitter/ shows they're now up to 0.8.1
> anyway.
> Also, I did a quick search of the codebase and am not sure python-twitter is
> actually in use. If it really is, can someone point out where?

I am fairly sure it was used in account at one point before Twitter
changed to OAuth. It was definitely used in zwitschern before it was
moved to django-microblogging. If used, it would be in social project.
I am not sure if removing it will break social project. Most likely
will. As a part of our fresh-start it will certainly be removed. I
believe we held the dependency at http://pypi.pinaxproject.com/ which
we should move to dist.pinaxproject.com which should solve the problem
you are seeing. I'll do that.

> More importantly, given the fresh-start branch and such, where should bugs
> be reported? Maybe I'll get slapped for saying this, but why not use
> github's issue tracking? :) Thanks.

We are working on a new CPC site which will be used for fresh-start.
We'll be announcing it hopefully very soon.