Re: Matt, what's the status of #562?

On Sun, Jan 28, 2018 at 11:48 PM, Matt Wilkie wrote: > 8b6f281 > > puts > the Pypi build and upload notes into nodes. > ​Many thanks for this. Rev 15035f2 contains the following minor

Re: Matt, what's the status of #562?

On Sun, Jan 28, 2018 at 11:26 PM, Matt Wilkie wrote: > Thanks for picking this up and pointing out the bits that aren't clear. > > > Is it really true, as you imply, that pyqt gets installed automatically > with python 3? Or have I misunderstood something? > > Yes that's

Re: Matt, what's the status of #562?

8b6f281 puts the Pypi build and upload notes into nodes. The "Matt's workflow for updating pypi" node can be deleted. I delayed doing so as I'm not sure we're finished with it? On Sun, Jan 28, 2018 at

Re: Matt, what's the status of #562?

Thanks for picking this up and pointing out the bits that aren't clear. > Is it really true, as you imply, that pyqt gets installed automatically with python 3? Or have I misunderstood something? Yes that's correct. There is a pypi PyQt wheel for py3.4+ but not for py2.7+. > - I have punted on

Re: Matt, what's the status of #562?

On Sat, Jan 27, 2018 at 3:20 AM, Edward K. Ream wrote: ​ > > I am presently in the midst of a careful revision of this first comment. >> This is likely the only way that I can understand all the details myself. >> Please review my changes. >> > > ​I have completed the

Re: Matt, what's the status of #562?

On Sat, Jan 27, 2018 at 2:41 AM, Edward K. Ream wrote: I am presently in the midst of a careful revision of this first comment. > This is likely the only way that I can understand all the details myself. > Please review my changes. > ​I have completed the revision. The

Re: Matt, what's the status of #562?

On Fri, Jan 26, 2018 at 12:21 PM, Matt Wilkie wrote: > ... (...just noticed a command mistake, fixing that shortly) >> > > Done. Top post updated and also internal documentation notes with commit > e1eae1f >

Re: Matt, what's the status of #562?

> > ... (...just noticed a command mistake, fixing that shortly) > Done. Top post updated and also internal documentation notes with commit e1eae1f to leoDist.leo->Discussions->Matt's workflow for updating

Re: Matt, what's the status of #562?

> > I believe it's now only: >> >>- Someone besides Matt runs through process from start to finish and >>is successful ;-) >> >> ​I don't have any idea what "the process" is, or what it's supposed to do. > Oh! Well that's certainly a problem. :) > So, what I am asking is for a revision

Re: Matt, what's the status of #562?

On Fri, Jan 26, 2018 at 12:01 AM, Viktor Ransmayr wrote: > > It's not clear to me, if you are interested in the user- or the developer >>> view on the status of this issue? >>> >> >> ​Both. I have no idea what this project attempts to do, how to describe >> it to

Re: Matt, what's the status of #562?

Hello Edward, 2018-01-26 0:40 GMT+01:00 Edward K. Ream : > On Thu, Jan 25, 2018 at 2:21 PM, Viktor Ransmayr < > viktor.ransm...@gmail.com> wrote: > > It's not clear to me, if you are interested in the user- or the developer >> view on the status of this issue? >> > > ​Both.

Re: Matt, what's the status of #562?

On Thu, Jan 25, 2018 at 2:21 PM, Viktor Ransmayr wrote: It's not clear to me, if you are interested in the user- or the developer > view on the status of this issue? > ​Both. I have no idea what this project attempts to do, how to describe it to users, or how to test

Re: Matt, what's the status of #562?

Hello Edward & Matt, Am Dienstag, 23. Januar 2018 12:06:17 UTC+1 schrieb Edward K. Ream: > > On Mon, Jan 22, 2018 at 11:53 AM, Matt Wilkie > wrote: > >> >> The discussion in #562 >>> is long. Could >>> you please

Re: Matt, what's the status of #562?

On Mon, Jan 22, 2018 at 11:53 AM, Matt Wilkie wrote: > > The discussion in #562 >> is long. Could >> you please summarize the present status and what, if anything, I might need >> to do. >> >> I would like to release the

Re: Matt, what's the status of #562?

> The discussion in #562 > is long. Could you > please summarize the present status and what, if anything, I might need to > do. > > I would like to release the next version of Leo once all this is resolved. > I believe it's now only: -

Matt, what's the status of #562?

The discussion in #562 is long. Could you please summarize the present status and what, if anything, I might need to do. I would like to release the next version of Leo once all this is resolved. Edward -- You received this message