VimPlug/jedi
1
0
Fork 1
mirror of https://github.com/davidhalter/jedi.git synced 2025-12-06 22:14:27 +08:00
Code Issues Actions Packages Projects Releases Wiki Activity

Move history

Browse Source
This commit is contained in:
Dave Halter
2020-03-19 02:16:21 +01:00
parent 2f651966e7
commit 83e0e3bd8d
2 changed files with 34 additions and 31 deletions
Download Patch File Download Diff File Expand all files Collapse all files

35
docs/docs/acknowledgements.rst
View File

@@ -1,7 +1,40 @@
.. include global.rst
History & Acknowledgements
==========================
A Little Bit of History
-----------------------
The Star Wars Jedi are awesome. My Jedi software tries to imitate a little bit
of the precognition the Jedi have. There's even an awesome `scene
<https://youtu.be/yHRJLIf7wMU>`_ of Monty Python Jedis :-).
But actually the name has not much to do with Star Wars. It's part of my
second name.
After I explained Guido van Rossum, how some parts of my auto-completion work,
he said (we drank a beer or two):
*"Oh, that worries me..."*
Now that it is finished, I hope he likes it :-)
I actually started Jedi back in 2012, because there were no good solutions
available for VIM. Most auto-completions just didn't work well. The only good
solution was PyCharm. But I like my good old VIM. Rope was never really
intended to be an auto-completion (and also I really hate project folders for
my Python scripts). It's more of a refactoring suite. So I decided to do my
own version of a completion, which would execute non-dangerous code. But I soon
realized, that this would not work. So I started working with a lot of
recursion to to understands many of Python's key features.
By the way, I really tried to program it as understandable as possible. But I
think understanding it might need quite some time, because of its recursive
nature.
Acknowledgements
================
----------------
- Takafumi Arakaki (@tkf) for creating a solid test environment and a lot of
other things.

30
docs/docs/features.rst
View File

@@ -108,33 +108,3 @@ execute properties and in general is not very careful to avoid code execution.
This is intentional: Most people trust the code bases they have imported,
because at that point a malicious code base would have had code execution
already.
A little bit of history
-----------------------
The Star Wars Jedi are awesome. My Jedi software tries to imitate a little bit
of the precognition the Jedi have. There's even an awesome `scene
<https://youtu.be/yHRJLIf7wMU>`_ of Monty Python Jedis :-).
But actually the name has not much to do with Star Wars. It's part of my
second name.
After I explained Guido van Rossum, how some parts of my auto-completion work,
he said (we drank a beer or two):
*"Oh, that worries me..."*
When it's finished, I hope he'll like it :-)
I actually started Jedi back in 2012, because there were no good solutions
available for VIM. Most auto-completions just didn't work well. The only good
solution was PyCharm. But I like my good old VIM. Rope was never really
intended to be an auto-completion (and also I really hate project folders for
my Python scripts). It's more of a refactoring suite. So I decided to do my
own version of a completion, which would execute non-dangerous code. But I soon
realized, that this wouldn't work. So I built an extremely recursive thing
which understands many of Python's key features.
By the way, I really tried to program it as understandable as possible. But I
think understanding it might need quite some time, because of its recursive
nature.