Re: [Jython-dev] Migrating to GitHub

[Adam B. <ada...@gm...>]

Basic test drives and sanity tests worked for me:

+ cloned new repo on a new (windows) machine
+ built from ant
+ ran gradle but got a deprecation warning which seems to be the current
state
+ spun up the console, did a few simple things
+ ran system tests and got current expected state

7 tests skipped:
    test_codecmaps_hk test_curses test_smtpnet test_socketserver
    test_subprocess test_urllib2net test_urllibnet
0 tests failed:

Platform:

'Java-13.0.2-OpenJDK_64-Bit_Server_VM,_13.0.2+8,_Oracle_Corporation-on-Windows_10-10.0-amd64'
Command line:

['C:\\Users\\burkeat\\jython\\jython1\\jython\\dist\\Lib\\test\\regrtest.py',
'-e', '-m', 'regrtest_memo.txt']

Cheers
Adam

On Fri, 5 Jun 2020 at 17:55, Jeff Allen <ja...@fa...> wrote:

> Welcome to your new home: https://github.com/jython/jython
>
> Take a look around. I'm sincerely hoping this works for us all, or is only
> wrong in ways we can put right. If you find this is irreparably messed up,
> we may be able to start over. Otherwise, I think this is where we now
> invite contribution and fix issues.
>
> After a day or two cooling off, I propse we ask the Ernest and the
> infrastructure team to make hg.python.org/jython read-only in some gentle
> way we could reverse if we had to.
>
> Anything other loose ends?
>
> Jeff
>
> Jeff Allen
>
> On 25/05/2020 16:42, Jeff Allen wrote:
>
> We've wanted to do this for ages. If you go back far enough, you can find
> Jim confidently asserting we'd use GitHub for 2.7.2 (
> https://sourceforge.net/p/jython/mailman/jython-dev/thread/CAOhO%3DaO_4GruQXQqmZk39a0C%3DXUnKyj%3DG6OcQtBkhtoQm9BCjw%40mail.gmail.com/#msg35054683
> ).
>
> Building with Gradle and accessing dependencies remotely (no JARs checked
> in) were identified as prerequisites at the time. In turn, I think building
> with Gradle requires re-organising the code to fit with its /convention
> over configuration/ idea (
> https://docs.gradle.org/current/userguide/organizing_gradle_projects.html#sec:use_standard_conventions).
> At least, doing otherwise in 2.7.2 got too difficult for me, somewhere
> around exposed classes ISTR.
>
> These don't seem to be prerequisites for the move. I would do Jython 3
> that way, but leave 2.7.3 as it is.
>
> https://bugs.jython.org/issue2892 opened to cover this. I'll try,
> starting withthe obvious way (
> https://help.github.com/en/github/importing-your-projects-to-github/importing-a-repository-with-github-importer)
> and reading what CPython did. I'd be happy to take input from anyone with a
> sure-fire answer.
>
> _______________________________________________
> Jython-dev mailing list
> Jyt...@li...
> https://lists.sourceforge.net/lists/listinfo/jython-dev
>