[IPython-dev] [Bug 215994] Re: We need to add the "complete" method to the Interpreter/Engine/Controller in IPython1
Fri Nov 14 15:30:22 CST 2008
Sorry about all of this. When I marked this ticket as "Won't Fix", I
did so for a very different reason. The main reason is that our
ticket system had lots of stale tickets and this was one of them. In
some cases I got rid of tickets that were "future work that we all
know needs to get done eventually."
So here is my intention and thoughts on the issue:
* The complete method *should* be in the backend.
* That doesn't prevent a given frontend from trying to implement
complete in a different, more efficint manner.
* This ticket is misleading as it will take a huge amount of
refactoring in the old ipython core to implement this properly. We
have *much* more to do that simply add the method.
* I want our tickets to be specific and detailed.
* This particular issue probably has 10 other things that need to be done first.
Things like this should probably go into a development blueprint in
our sphinx docs with notes on everything that needs to happen. But
until someone has lots of time to put into the refactoring, I guess I
would rather have our ticket list be more focused.
Does this make sense?
On Fri, Nov 14, 2008 at 9:31 AM, Barry Wark <email@example.com> wrote:
> On Fri, Nov 14, 2008 at 8:44 AM, Ville M. Vainio <firstname.lastname@example.org> wrote:
>> On Thu, Nov 13, 2008 at 7:28 AM, Barry Wark <email@example.com> wrote:
>>> I agree with the decision to push completion into the frontends.
>>> However, now we need to think about how the frontend is to gain
>>> knowlege of the relevant namespace (presumably the user wants the
>>> completion to be relevant for the namespace where the command will
>>> eventually be executed, not for the frontend). Observing namespace
>> I don't really see the point of doing it in the frontend, since it's
>> clearly a "model" level feature, and can't be reliably done in
>> frontend. What about custom completers etc.?
> Because the engine may be remote, I believe the consensus was that no
> one wanted to take the chance that there would be no completions
> available due to network lag or outage.
>> Ville M. Vainio
> IPython-dev mailing list
More information about the IPython-dev