On 30/10/2019 11:18, Kamil Rytarowski wrote:
On 30.10.2019 11:06, Pavel Labath wrote:
On 29/10/2019 21:40, Christos Zoulas wrote:
On Oct 29, 6:54pm, pa...@labath.sk (Pavel Labath) wrote:
-- Subject: Re: [lldb-dev] issue with lldb9 and python3.5
| On 29/10/2019 09:31, Serge Guelton via lldb
On 30.10.2019 11:06, Pavel Labath wrote:
> On 29/10/2019 21:40, Christos Zoulas wrote:
>> On Oct 29, 6:54pm, pa...@labath.sk (Pavel Labath) wrote:
>> -- Subject: Re: [lldb-dev] issue with lldb9 and python3.5
>>
>> | On 29/10/2019 09:31, Serge Guelton via lldb-dev w
On 29/10/2019 21:40, Christos Zoulas wrote:
On Oct 29, 6:54pm, pa...@labath.sk (Pavel Labath) wrote:
-- Subject: Re: [lldb-dev] issue with lldb9 and python3.5
| On 29/10/2019 09:31, Serge Guelton via lldb-dev wrote:
| > On Mon, Oct 28, 2019 at 10:09:53AM -0700, Adrian McCarthy wrote:
| &g
On 29.10.2019 21:40, Christos Zoulas wrote:
> On Oct 29, 6:54pm, pa...@labath.sk (Pavel Labath) wrote:
> -- Subject: Re: [lldb-dev] issue with lldb9 and python3.5
>
> | On 29/10/2019 09:31, Serge Guelton via lldb-dev wrote:
> | > On Mon, Oct 28, 2019 at 10:09:53AM -0700, Adr
On 29/10/2019 09:31, Serge Guelton via lldb-dev wrote:
On Mon, Oct 28, 2019 at 10:09:53AM -0700, Adrian McCarthy wrote:
+1 Yes, for Windows, I'd be happy if we said Python 3.6+.
I investigated the bug yesterday, and filled some of my discoveries in
https://bugs.llvm.org/show_bug.cgi?id=4
On Mon, Oct 28, 2019 at 10:09:53AM -0700, Adrian McCarthy wrote:
> +1 Yes, for Windows, I'd be happy if we said Python 3.6+.
I investigated the bug yesterday, and filled some of my discoveries in
https://bugs.llvm.org/show_bug.cgi?id=43830
TLDR: libpython uses libreadline and lldb uses libed
McCarthy
via lldb-dev
Sent: Monday, October 28, 2019 12:10 PM
To: Jonas Devlieghere
Cc: Serge Guelton ; LLDB Dev
Subject: [EXT] Re: [lldb-dev] issue with lldb9 and python3.5
+1 Yes, for Windows, I'd be happy if we said Python 3.6+.
On Mon, Oct 28, 2019 at 10:07 AM Jonas Devlieghere via lld
+1 Yes, for Windows, I'd be happy if we said Python 3.6+.
On Mon, Oct 28, 2019 at 10:07 AM Jonas Devlieghere via lldb-dev <
lldb-dev@lists.llvm.org> wrote:
> On Mon, Oct 28, 2019 at 10:04 AM Jonas Devlieghere
> wrote:
> >
> > On Mon, Oct 28, 2019 at 9:32 AM Tom Stellard
> wrote:
> > >
> > > On
On Mon, Oct 28, 2019 at 10:04 AM Jonas Devlieghere
wrote:
>
> On Mon, Oct 28, 2019 at 9:32 AM Tom Stellard wrote:
> >
> > On 10/28/2019 09:29 AM, Jonas Devlieghere wrote:
> > > Yes, Python 3.5 is not supported. We "officially" support Python 2.7
> > > and Python 3.7. I'm sorry if we forgot that i
On Mon, Oct 28, 2019 at 9:32 AM Tom Stellard wrote:
>
> On 10/28/2019 09:29 AM, Jonas Devlieghere wrote:
> > Yes, Python 3.5 is not supported. We "officially" support Python 2.7
> > and Python 3.7. I'm sorry if we forgot that in the release notes.
> >
>
> Is there a specific reason why 3.5 is not
On 10/28/2019 09:29 AM, Jonas Devlieghere wrote:
> Yes, Python 3.5 is not supported. We "officially" support Python 2.7
> and Python 3.7. I'm sorry if we forgot that in the release notes.
>
Is there a specific reason why 3.5 is not supported? Is it
because of this issue?
-Tom
> On Mon, Oct 28,
Yes, Python 3.5 is not supported. We "officially" support Python 2.7
and Python 3.7. I'm sorry if we forgot that in the release notes.
On Mon, Oct 28, 2019 at 7:06 AM Tom Stellard via lldb-dev
wrote:
>
> + lldb-dev
>
> On 10/28/2019 07:06 AM, Tom Stellard wrote:
> > On 10/28/2019 03:50 AM, Romari
+ lldb-dev
On 10/28/2019 07:06 AM, Tom Stellard wrote:
> On 10/28/2019 03:50 AM, Romaric Jodin via lldb-dev wrote:
>> Hi everyone,
>>
>> I have lldb crashing since I've updated to lldb9. Seems like there is a
>> issue with python3.5. Everything seems to work fine with python3.7.
>> Am I missing s
13 matches
Mail list logo