Re: Import python 3.7

I generally work fast and careful, and the docs are lacking on how to find dependencies (unless I am missing it). As noted previously though there are a large number of things outdated, so of course submissions will be in batches, not sure how you expect this worked around. If there is a

Re: Import python 3.7

On 2018/11/20 17:11, Edward Lopez-Acosta wrote: > Stuart, > > I did some thinking on this as a heavy consumer, and light developer, of > Python applications. > > There are 455 Python3 modules currently in the repository would would be > unreasonable to test all of them [1]. Yes it would be

Re: Import python 3.7

Stuart, I did some thinking on this as a heavy consumer, and light developer, of Python applications. There are 455 Python3 modules currently in the repository would would be unreasonable to test all of them [1]. That being said there also appears to be hesitation on importing updated

Re: Import python 3.7

I am in agreement with the replacement. The symlink was a suggestion if for some reason people want to have both available. On Thursday, November 15, 2018, Stuart Henderson wrote: > On 2018/11/15 09:58, Edward Lopez-Acosta wrote: >> Daniel your update builds and runs fine for me on amd64. >> >>

Re: Import python 3.7

On 2018/11/15 09:58, Edward Lopez-Acosta wrote: > Daniel your update builds and runs fine for me on amd64. > > Two notes though: > > Current version is now 3.7.1, I tested and same patches apply to this > version. > > Second is if we have side by side installs then /usr/local/bin/python3 >

Import python 3.7

Daniel your update builds and runs fine for me on amd64. Two notes though: Current version is now 3.7.1, I tested and same patches apply to this version. Second is if we have side by side installs then /usr/local/bin/python3 should be a symlink to the users preferred version. Not owned by a

Re: import python 3.7

On Thu Sep 27, 2018 at 07:35:50AM -0400, Daniel Jakots wrote: > On Tue, 18 Sep 2018 20:21:01 -0400, Daniel Jakots > wrote: > > > On Tue, 11 Sep 2018 22:19:13 -0400, Daniel Jakots > > wrote: > > > > > On Sat, 8 Sep 2018 14:28:06 -0400, Daniel Jakots > > > wrote: > > > > > > > Does the test

Re: import python 3.7

On Tue, 18 Sep 2018 20:21:01 -0400, Daniel Jakots wrote: > On Tue, 11 Sep 2018 22:19:13 -0400, Daniel Jakots > wrote: > > > On Sat, 8 Sep 2018 14:28:06 -0400, Daniel Jakots > > wrote: > > > > > Does the test suite work for you? In my case it seems it never > > > ends with "running:

Re: import python 3.7

On Tue, 11 Sep 2018 22:19:13 -0400, Daniel Jakots wrote: > On Sat, 8 Sep 2018 14:28:06 -0400, Daniel Jakots > wrote: > > > Does the test suite work for you? In my case it seems it never ends > > with "running: test_asyncio (2 min 52 sec)" until I ^c. If people > > have the same, I'll add

Re: import python 3.7

On Tue, 11 Sep 2018 22:19:13 -0400, Daniel Jakots wrote: > New tgz attached because the plist needed some @comment. ping

Re: import python 3.7

On Sat, 8 Sep 2018 14:28:06 -0400, Daniel Jakots wrote: > Does the test suite work for you? In my case it seems it never ends > with "running: test_asyncio (2 min 52 sec)" until I ^c. If people > have the same, I'll add TEST_IS_INTERACTIVE=Yes I looked into it and didn't find any solution. It

Re: import python 3.7

On Sat, Sep 08, 2018 at 02:28:06PM -0400, Daniel Jakots wrote: > Hey, > > I'd like to have python 3.7 for 6.4 (not as the default version of > course) and somewhere during 6.4 cycle we could switch over to it for > our python ports. > > I took 3.6 and adapted it for the new version. > > Does

import python 3.7

Hey, I'd like to have python 3.7 for 6.4 (not as the default version of course) and somewhere during 6.4 cycle we could switch over to it for our python ports. I took 3.6 and adapted it for the new version. Does the test suite work for you? In my case it seems it never ends with "running: