[SciPy-Dev] Submitting patches, updates

Vincent Davis vincent@vincentdavis....
Fri Jun 25 20:47:12 CDT 2010


On Fri, Jun 25, 2010 at 7:46 PM,  <josef.pktd@gmail.com> wrote:
> On Fri, Jun 25, 2010 at 9:36 PM, Vincent Davis <vincent@vincentdavis.net> wrote:
>> About 1.5 weeks ago I posted an email at the end of an email tread
>> saying I have updated codata.py to the 2006 physical constants. It
>> might have been missed since it was at the end of a tread and I am
>> sure it is of low priority. But my question is what it the right way
>> to submit a patch our updates?
>> Should they be announced as an separate email?
>> Should I submit a diff?
>> I bring this up as I was waiting for the code to be updated before I
>> completed the update to the docs for this file.
>> http://github.com/vincentdavis/SciPy-vmd-dev/blob/master/scipy/constants/codata.py
>
> Did you open a ticket?
> The usual is to open a ticket, and attach a patch, or a file with the
> new code, and a link to your branch if available, so it can be
> reviewed and committed and doesn't get lost in the mailing list.

No I did not, I will do that.
Thanks for the info.

Vincent
>
> Josef
>
>>
>> Thanks
>> Vincent
>> _______________________________________________
>> SciPy-Dev mailing list
>> SciPy-Dev@scipy.org
>> http://mail.scipy.org/mailman/listinfo/scipy-dev
>>
> _______________________________________________
> SciPy-Dev mailing list
> SciPy-Dev@scipy.org
> http://mail.scipy.org/mailman/listinfo/scipy-dev
>


More information about the SciPy-Dev mailing list