Re: [Scons-users] SCons 3.0, sconsign files and Py2 vs Py3.. how to handle sconsign imcompatabilities
Dirk Baechle <[email protected]>
| Newsgroups | gmane.comp.programming.tools.scons.devel |
|---|---|
| Message-ID | <[email protected]> |
Bill, thanks for clarifying and it's fine with me to wait. Should I open the PR still on Bitbucket/hg then, or is there already a plan for the switch to Github right after v3.0? Regards, Dirk Am 11. September 2017 14:59:48 MESZ schrieb Bill Deegan <[email protected]>: >Dirk, > >I'd rather push that change to 3.1 (The need for speed release). >That'll also give us time for some betas with those changes. > >-Bill > >On Mon, Sep 11, 2017 at 5:43 AM, Dirk Baechle <[email protected]> wrote: > >> Hi Bill, >> >> Am 10. September 2017 04:13:37 MESZ schrieb Bill Deegan < >> [email protected]>: >> >Greetings, >> > >> >This is (I hope) the last issue gating 3.0 release. >> > >> >Thoughts? >> > >> >> not about this issue, but can we try to get the "stubprocess.py" >wrapper >> from Parts integrated for v3.0? I'm working on this and will try to >create >> a PR tonight. Unless you think this feature is still "too hot" and >would >> need more testing first. >> >> Best regards, >> >> Dirk >> >> -- >> Sent from my Android with K-9 Mail. >> -- Sent from my Android with K-9 Mail. _______________________________________________ Scons-dev mailing list [email protected] https://pairlist2.pair.net/mailman/listinfo/scons-dev