[Chicago] Julython

Adam "Cezar" Jenkins emperorcezar at gmail.com
Mon Jul 2 04:31:00 CEST 2012


You do have to fork to do a pull request. An issue would be something else
you do. The github team, when coding github, will usually do a very
barebones code up, start a pull request, and use the pull request to
discuss the issue and make changes.

That said, I looked at the code and they are using app engine.
https://github.com/rmyers/gae_django/blob/master/auth/backend.py
So the twitter backend is built in.

On Sun, Jul 1, 2012 at 9:14 PM, Mark Johnson <luther07 at gmail.com> wrote:

> If I'm not mistaken, first you have to fork the site and implement the
> feature before doing a pull request.
>
>
> On Sun, Jul 1, 2012 at 9:00 PM, Adam "Cezar" Jenkins <
> emperorcezar at gmail.com> wrote:
>
>> Github would be great. I think they have the code for the site up, maybe
>> a pull request?
>>
>> I have a guess they might be using a lot of twitter features, but I could
>> be totally wrong.
>>
>>
>> On Sun, Jul 1, 2012 at 8:36 PM, Bob Haugen <bob.haugen at gmail.com> wrote:
>>
>>> Or for this purpose, why not github?
>>> _______________________________________________
>>> Chicago mailing list
>>> Chicago at python.org
>>> http://mail.python.org/mailman/listinfo/chicago
>>>
>>
>>
>> _______________________________________________
>> Chicago mailing list
>> Chicago at python.org
>> http://mail.python.org/mailman/listinfo/chicago
>>
>>
>
> _______________________________________________
> Chicago mailing list
> Chicago at python.org
> http://mail.python.org/mailman/listinfo/chicago
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/chicago/attachments/20120701/db1e15a9/attachment.html>


More information about the Chicago mailing list