You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi all, it's not really an issue, but we face to a situation where we have many forks and a dead upstream (sciyoshi). Maybe I've not understand the whole power of github, but I never know which fork to merge to find the function I want. I'm never sure that I implement something new or lacking.
Is there any solution to this, or shall we define a new fork as upstream and update the doc consequently ?
For information, I've merged Mrbouyou's fork.
The text was updated successfully, but these errors were encountered:
Actually, I think it's a real problem and needs to be figured out, especially in the light of the new Graph API and the official SDK at http://github.com/facebook/python-sdk/. Are there any leads wrt the future of pyfacebook?
I'm using mirumee's fork as the current 'most-up-to-date' - seems to have merged most others, and has oauth2. http://github.com/mirumee/pyfacebook
Agree with jezdez that it is a problem - would like to carry on using pyfacebook, but if there's confusion over its future, the official SDK may have to be focus from now on...
Hi all, it's not really an issue, but we face to a situation where we have many forks and a dead upstream (sciyoshi). Maybe I've not understand the whole power of github, but I never know which fork to merge to find the function I want. I'm never sure that I implement something new or lacking.
Is there any solution to this, or shall we define a new fork as upstream and update the doc consequently ?
For information, I've merged Mrbouyou's fork.
The text was updated successfully, but these errors were encountered: