From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: =?UTF-8?Q?=D0=90=D0=BD=D0=B4=D1=80=D0=B5=D0=B9_?= =?UTF-8?Q?=D0=9F=D0=B0=D1=80=D0=B0=D0=BC=D0=BE=D0=BD=D0=BE=D0=B2?= Newsgroups: gmane.emacs.bugs Subject: bug#28580: python.el: native completion setup failed Date: Sun, 24 Sep 2017 23:34:07 +0300 Message-ID: References: <87lgl4m5uo.fsf@users.sourceforge.net> <87a81km1d4.fsf@users.sourceforge.net> <877ewom0id.fsf@users.sourceforge.net> <874lrrnaxq.fsf@users.sourceforge.net> <871smvn9oo.fsf@users.sourceforge.net> <87y3p3ltzx.fsf@users.sourceforge.net> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="001a11444cce81f6140559f55fe1" X-Trace: blaine.gmane.org 1506285319 21503 195.159.176.226 (24 Sep 2017 20:35:19 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Sun, 24 Sep 2017 20:35:19 +0000 (UTC) Cc: 28580@debbugs.gnu.org To: Noam Postavsky Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Sun Sep 24 22:35:10 2017 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dwDcG-0004lD-NM for geb-bug-gnu-emacs@m.gmane.org; Sun, 24 Sep 2017 22:35:04 +0200 Original-Received: from localhost ([::1]:39333 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dwDcN-0007IF-Uk for geb-bug-gnu-emacs@m.gmane.org; Sun, 24 Sep 2017 16:35:11 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:59956) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dwDcH-0007Hf-IQ for bug-gnu-emacs@gnu.org; Sun, 24 Sep 2017 16:35:06 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dwDcE-0004d0-Ee for bug-gnu-emacs@gnu.org; Sun, 24 Sep 2017 16:35:05 -0400 Original-Received: from debbugs.gnu.org ([208.118.235.43]:47895) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1dwDcE-0004cY-BR for bug-gnu-emacs@gnu.org; Sun, 24 Sep 2017 16:35:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1dwDcE-000322-4w for bug-gnu-emacs@gnu.org; Sun, 24 Sep 2017 16:35:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: =?UTF-8?Q?=D0=90=D0=BD=D0=B4=D1=80=D0=B5=D0=B9_?= =?UTF-8?Q?=D0=9F=D0=B0=D1=80=D0=B0=D0=BC=D0=BE=D0=BD=D0=BE=D0=B2?= Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sun, 24 Sep 2017 20:35:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 28580 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 28580-submit@debbugs.gnu.org id=B28580.150628529411638 (code B ref 28580); Sun, 24 Sep 2017 20:35:02 +0000 Original-Received: (at 28580) by debbugs.gnu.org; 24 Sep 2017 20:34:54 +0000 Original-Received: from localhost ([127.0.0.1]:56576 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dwDc6-00031d-MX for submit@debbugs.gnu.org; Sun, 24 Sep 2017 16:34:54 -0400 Original-Received: from mail-qk0-f173.google.com ([209.85.220.173]:52713) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dwDc5-00031R-7A for 28580@debbugs.gnu.org; Sun, 24 Sep 2017 16:34:53 -0400 Original-Received: by mail-qk0-f173.google.com with SMTP id o77so5001794qke.9 for <28580@debbugs.gnu.org>; Sun, 24 Sep 2017 13:34:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=btMAVfQuuSjkvEuZUotAs6695C28hQENflvJ8MLu6kc=; b=atnoYnl8X3dIgaQtLubtlgM+jOJzqCN3R4VV7mx5+IY8n2jkoBnl/vpgN99hH2B2Y2 Y8HI/gDnAXeY5D3gIQrsd/+7BwCUIbexl4jIYu4F3pHR5Rn0Ell+q7NiCHDT1MDhf0HY f8y0+qSseBNO0A416875sLjKemmwP4TUvoax7y3aDrTRDDfLPPRhPEqVwX30KoJ37C/l +w8iqTiNVO5wXgktNh9GDCCfMLFaypEcg+dc9ibbFndidi6pD8TD/XW3ZUKH7wTx0QxO gKZoHP2/Zsw7o30JwMluVwfKj4OLcWNeTf/rvcGxnWXIVMGfIsA/wSqnuT7kEoJ7dcD7 ngrg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=btMAVfQuuSjkvEuZUotAs6695C28hQENflvJ8MLu6kc=; b=mVMVEOPttPE0uXKJItc/7R1fBtWCbFKV5JLh0f92TSSztoDNYSfJa/qTMm8PFMzgXX dZQb3fyfRbkIlNzzMVCTQA+kMj6BvFBr7FqvaZ4vexUDcBRIH0vw7/ZV5SIwMZzN1b/m +siZXVaEpvJirWOoXAQlRw7DQKFxvIflMcTBdUsfl7BRl0S3HlqcDMiK5/mp725P7E8V zjdjmEm2EaSjjnO9sFqDZJgCHatyMYOG6RSTdk2zaUdHdbzVtUxFt4+EACT6fBsYKWVb pSo7i+Zr6sYfcW4Iil9wb2C2RzZb4b3qTuDBf3rdZdQOouI0bSlOZXhNoxbZ0jEQmARR h2hg== X-Gm-Message-State: AHPjjUjgoLO0eVHmTODnUupdYcm2sUOHGMci8vvDhy95e0ZmTobIhZH7 5RYDaXfE2g5SxDDJ2GZ7BKYEZi7fw3ECmMqsBzU= X-Google-Smtp-Source: AOwi7QCxMXM46/IlHnPUmllH6i5N9DkeLckMwp7h/Kr7wVd5nAlCwaXUCfdC5rsOukP61wa4WaYlmL+1uTpuGh9tjyg= X-Received: by 10.55.27.145 with SMTP id m17mr7182215qkh.243.1506285287763; Sun, 24 Sep 2017 13:34:47 -0700 (PDT) Original-Received: by 10.200.43.88 with HTTP; Sun, 24 Sep 2017 13:34:07 -0700 (PDT) In-Reply-To: <87y3p3ltzx.fsf@users.sourceforge.net> X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 208.118.235.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.org gmane.emacs.bugs:137365 Archived-At: --001a11444cce81f6140559f55fe1 Content-Type: text/plain; charset="UTF-8" 2017-09-24 23:30 GMT+03:00 Noam Postavsky : > Can you clarify, if you just run M-x run-python without doing anything > with "t.py" you see the "python.el: native completion setup loaded" or > the "python.el: native completion setup failed" message? > I see now >>> python.el: native completion setup loaded > The "native" completion might still be disabled, and you're actually > using the "fallback" method. > That should be suboptimal -- otherwise why the warning? What could make the "native" completion fail? How to check if it's really the case? Best wishes, Andrey Paramonov --001a11444cce81f6140559f55fe1 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
2017= -09-24 23:30 GMT+03:00 Noam Postavsky <npostavs@users.sourcef= orge.net>:
Can you clarify, if you just run M-x run-python without doing anyth= ing
with "t.py" you see the "python.el: native completion setup = loaded" or
the "python.el: native completion setup failed" message?

I see now
>>> python.el: nat= ive completion setup loaded=C2=A0
=C2=A0
The "native" completion might st= ill be disabled, and you're actually
using the "fallback" method.

That should be subo= ptimal -- otherwise why the warning?
What c= ould make the "native" completion fail? How to check if it's = really the case?

Best wishes,
Andrey Paramonov

--001a11444cce81f6140559f55fe1--