Re: Where should sandbox/jython3 live?

Adding myself back into the conversation :)

IronPython has been on GitHub for a while (almost 5 years), and it's
been brilliant. Concerns over lockin and etc. are completely
overblown; if we escaped from CodePlex, we can escape whatever lockin
GitHub tries to institute.

It *would* be nice to have a single stdlib repo, though. The current
ironpython3 repo stores it in a vendor branch, but I think this is one
case where having a submodule would work better. I just didn't bother
because I didn't have anyone to share it with. A couple of scripts and
hg-git should take care of keeping it up-to-date.

- Jeff

On Fri, May 8, 2015 at 12:36 AM, Jim Baker <[email protected]> wrote:
> I don't think we care so much about the heatedness of that discussion :)
> Practicality over purity, I suppose...
>
> On the one hand, I would like to use the new CPython tooling that is
> currently being discussed. Unfortunately, as I learned at the PyCon sprints,
> the plan of this tooling will itself not see initial review until late this
> summer.
>
> On the other hand, we are not such a big project like CPython, we certainly
> don't have the resources, and we would like to minimize our admin costs,
> because that subtracts from actual dev time! Current dev is just too
> painful, especially accepting PRs.
>
> Any number of critical Python projects, such as PyPA are now on GitHub. In
> our case, we still own the repos, we can still mirror against
> hg.python.org/jython, and moving the authoritative git repos is trivial
> somewhere else, once we as a group agree. There is minimal lock-in, in other
> words, other than our own inertia.
>
> - Jim
>
>
> On Thu, May 7, 2015 at 4:56 PM, Jeff Allen <[email protected]> wrote:
>>
>> There was a long discussion on python-dev of moving CPython to GitHub
>> (or BItBucket, or ...) which most of us probably saw. It was fairly
>> heated, including objections concerning "FLOSS ethics" and lock-in. The
>> outcome was to stick with PSF infrastructure for CPython, as we see, but
>> there was a plan to move the documentation to a free (as in beer) service.
>>
>> I don't feel strongly, but wouldn't all the arguments apply equally to
>> Jython?
>>
>> +1 for having all versions in the same official repo.
>>
>> Jeff Allen
>>
>>
>> On 07/05/2015 18:13, [email protected] wrote:
>> > On Thu, May 7, 2015 at 10:08 AM, [email protected]
>> > <[email protected]> wrote:
>> >> On Thu, May 7, 2015 at 10:06 AM, [email protected]
>> >> <[email protected]> wrote:
>> >>
>> >>> The wacky part is that I'm maintaining a 2.7 compatible version in
>> >>> https://github.com/jython/jy3k.
>> >> That was a typo/braino, don't get excited. It should have been:
>> >> https://hg.python.org/sandbox/jy3k/ which is a very old branch I
>> >> started years ago.
>> > I guess we could make the sandbox branch a real branch in our main hg
>> > repo. Would that help?
>> >
>> > P.S. I took Jeff off of the CC: and changed the subject since we are
>> > way off of the announcement topic now :)
>> >
>> > -Frank
>> >
>> >
>> > ------------------------------------------------------------------------------
>> > One dashboard for servers and applications across Physical-Virtual-Cloud
>> > Widest out-of-the-box monitoring support with 50+ applications
>> > Performance metrics, stats and reports that give you Actionable Insights
>> > Deep dive visibility with transaction tracing using APM Insight.
>> > http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
>> > _______________________________________________
>> > Jython-dev mailing list
>> > [email protected]
>> > https://lists.sourceforge.net/lists/listinfo/jython-dev
>> >
>>
>>
>>
>> ------------------------------------------------------------------------------
>> One dashboard for servers and applications across Physical-Virtual-Cloud
>> Widest out-of-the-box monitoring support with 50+ applications
>> Performance metrics, stats and reports that give you Actionable Insights
>> Deep dive visibility with transaction tracing using APM Insight.
>> http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
>> _______________________________________________
>> Jython-dev mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/jython-dev
>
>
>
>
> --
> - Jim
>
> jim.baker@{colorado.edu|python.org|rackspace.com|zyasoft.com}
> twitter.com/jimbaker
> github.com/jimbaker
> bitbucket.com/jimbaker
>
> ------------------------------------------------------------------------------
> One dashboard for servers and applications across Physical-Virtual-Cloud
> Widest out-of-the-box monitoring support with 50+ applications
> Performance metrics, stats and reports that give you Actionable Insights
> Deep dive visibility with transaction tracing using APM Insight.
> http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
> _______________________________________________
> Jython-dev mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/jython-dev
>

------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud 
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y