Re: Contribution info?

Hello Ray,
thank you for your interest in contributing to Jython!
Since github's web interface is better suited to review and discuss code
patches than the issue tracker (BJO), you might want to file a PR for each
patch on the github mirror https://github.com/jythontools/jython. This is
meant in addition to tracking at http://bugs.jython.org/. (Please crosslink
your PR there.)
This is especially a good option in case you already host your patches on
github.

Best

-Stefan


Am So., 30. Sep. 2018 um 20:09 Uhr schrieb Jeff Allen <[email protected]>:

> Welcome Ray.
>
> http://bugs.jython.org/ is the place. Please open an issue for each.
>
> I have seen some people have difficulty creating an account, and I don't
> know why. Come back here if you do and we'll try a second option. We
> wouldn't want to lose your input for a silly reason.
>
> Jeff Allen
>
> On 30/09/2018 17:59, Raymond Ferguson via Jython-dev wrote:
>
> I've tracked down a bug in Lib/zip that I have a patch for.  I'm not sure
> how to collaborate with the jython team?  Do you want patches sent here or
> bug reports etc?
>
> Basically the strip_header variation still leaves CRC32|ISIZE bytes on the
> tail which is seen as a decompression failure by upstream modules.
>
> I also have an upstream patch for python-msgpack and a shaded version in
> the latest pip release that brings pip-18.0 to jython!
>
> Thank you for the work.
>
> Sincerely,
>
> *Ray Ferguson*
> *Enterprise Solutions Developer*
> *Devendor Tech LLC*
> *[email protected]* <[email protected]>
> *W: 608-960-8090 C: 608-516-9391*
>
> ᐧ
>
>
> _______________________________________________
> Jython-dev mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/jython-dev
>

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