Re: Questions on Getting Started

Thanks for the detailed reply, I'll try to get something done over the long
weekend thats coming up.

On Wed, Apr 1, 2015 at 8:36 PM, Jim Baker <[email protected]> wrote:

> Gautam,
>
> Thanks for taking a look! Let me answer what I can below:
>
> On Tue, Mar 31, 2015 at 8:25 PM, Gautam Kumar <[email protected]>
> wrote:
>
>> Hi,
>>
>> I'm trying to get started with contributing to Jython, I have a few
>> questions,
>>
>> 1. Which Developer Guide is considered the primary ?
>>
>> https://wiki.python.org/jython/JythonDeveloperGuide
>>
>>
> This is the original dev guide, and it contains some very practical
> information for any Jython developer, no matter how experienced.
>
>
>>  OR
>> http://www.jython.org/devguide/ ?
>>
>>
> This is a work-in-progress port of the CPython dev guide. It's a great
> format, and contains useful information for a new developer, but it's less
> in-depth about Jython internals than the above guide.
>
>
>> 2. I noticed that there was a github (
>> https://github.com/jythontools/jython) mirror, Is it
>> being actively used ?
>>
>
> Yes.
>
>
>>
>> Would it be alright if I fork and sent patches as pull requests ?
>>
>
> Please file a bug against http://bugs.jython.org/ so we can track if you
> do so. Pull requests by themselves really don't have the context we need,
> especially for prioritization. (Occasionally I have committed a lower
> priority change as we wrap up 2.7.0, but I'm trying to stay disciplined and
> focus only on urgent bugs at this point.)
>
> FWIW, the use of bitbucket for PRs is discouraged because it's really time
> consuming to get a usable diff that we can commit, just due to how
> hg.python.org is managed.
>
> Lastly, I personally consider myself a terrible, nonscalable select loop
> ;) - there's more email, pull requests on github and bitbucket, bugs,
> tweets, IRCs, etc, than I could ever respond to, and that's just my Jython
> work. Other Jython developers here are in the same situation.
>
>
>> I'm struggling with mercurial at the moment.
>>
>
> One goal of the next dev cycle (2.7.1) is to transition to
> https://github.com/jython - as you can see it's waiting to be filled in.
> Something we will work on during the PyCon sprints for sure!
>
>
>> 3. Any recommendations of easy issues that I can try to fix ?
>> I was thinking maybe
>> http://bugs.jython.org/issue1376 ?
>>
>
> That's a good one, because it does go into internals, such as __dir__ vs
> __rawdir__, but it's not so difficult either. Trace this through its
> implementation in PyObject and other places that override it in the
> inheritance hierarchy. Good luck, we hope to see a good PR! Specifically if
> you do tackle http://bugs.jython.org/issue1376, mention your PR there.
>
> One more thing: the best way to get help is to hang out on #jython on
> freenode and ask questions - and ideally answer them!
>
> - Jim
>
>

------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/

_______________________________________________
Jython-dev mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jython-dev