homepage

This issue tracker has been migrated to GitHub , and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author terry.reedy
Recipients Saimadhav.Heblikar, THRlWiTi, Todd.Rovito, philwebster, terry.reedy
Date 2016年07月25日.02:35:41
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1469414142.52.0.890234668826.issue18766@psf.upfronthosting.co.za>
In-reply-to
Content
I opened #27609 to keep track of multiple completion issues. Some additions to what I said above.
1. I would like to move the actual fetch code to run.py, since it is normally executed in the user process. See #27534, but also below.
2. Idle currently differentiates between completion invocation by <tab> or '.' and by <<force-completions>>, which defaults to Cntl-space. I believe a main difference is that it will only call functions in the object expression, as in "f().", in the latter case. I believe the distinction operates by calling for completions or not. (I need to check.) 
That distinction can be used here by only importing with <<force-completion>>, and then it should. With that limitation, I think I am now in favor of adding this. Importing a module is roughly equivalent to calling a function. Either can do anything. But the distinction has be known within the fetch code. This could be done with a wrapper function.
History
Date User Action Args
2016年07月25日 02:35:42terry.reedysetrecipients: + terry.reedy, THRlWiTi, Todd.Rovito, philwebster, Saimadhav.Heblikar
2016年07月25日 02:35:42terry.reedysetmessageid: <1469414142.52.0.890234668826.issue18766@psf.upfronthosting.co.za>
2016年07月25日 02:35:42terry.reedylinkissue18766 messages
2016年07月25日 02:35:41terry.reedycreate

AltStyle によって変換されたページ (->オリジナル) /