On Thu, Aug 2, 2018 at 3:50 PM Burton, Ross wrote:
> The last to be inherited behaviour? That's the same as the current
> behaviour, apart from after my change both pythons are available via
> PATH.
>
> The only change is that inheriting the second class doesn't wipe out
> the first class.
Ok
The last to be inherited behaviour? That's the same as the current
behaviour, apart from after my change both pythons are available via
PATH.
The only change is that inheriting the second class doesn't wipe out
the first class.
Ross
On 2 August 2018 at 22:05, Khem Raj wrote:
>
>
> On Tue, Jul
On Tue, Jul 31, 2018 at 10:06 AM Ross Burton wrote:
> Instead of both classes using ${PYTHON_PN} (which is set by python-dir and
> python3-dir), hardcode the right values so that it is possible to inherit
> both
> pythonnative and python3native at the same time.
>
> If both are inherited then
Instead of both classes using ${PYTHON_PN} (which is set by python-dir and
python3-dir), hardcode the right values so that it is possible to inherit both
pythonnative and python3native at the same time.
If both are inherited then both native Pythons are available, but the last to be
inherited
