davidhalter/jedi-vim

Using the jedi autocompletion library for VIM.

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 41 minutes ago
Added to GitGenius on September 12th, 2026
Created on September 18th, 2012
Open Issues & Pull Requests: 31 (+0)
GitHub issues: Enabled
Number of forks: 369
Total Stargazers: 5,306 (+0)
Total Subscribers: 107 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 3.8 hours
Mean response time: 8.1 days
90th percentile: 6.6 days
Tracked items: 15

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 3
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 2,090 days
Stale 30+ days: 3
Stale 90+ days: 3

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • discussion (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

jedi-vim is a VIM plugin that provides Python autocompletion using the Jedi library.

The tool solves the problem of writing Python code efficiently in VIM by integrating Jedi's static analysis engine. It offers completion triggered by Ctrl+Space, goto assignment and definition commands, documentation display with syntax highlighting, renaming support, and usage finding. The plugin works by binding VIM to Jedi's autocompletion library, which understands Python's core language features including decorators and generators.

Developers should be aware that jedi-vim is in maintenance mode and the maintainer recommends newer alternatives for new projects. The tool requires VIM compiled with Python 3 support or Neovim with pynvim installed. It suits developers who already use VIM and want Python-aware editing without switching to a language server protocol setup. The README explicitly recommends considering other solutions that offer faster performance and better typing support.

The project receives pull requests and maintains a contribution guide, indicating ongoing community engagement. The repository includes automated testing via continuous integration workflows. The maintainer has explicitly communicated that the project is in maintenance mode with no plans to add new features, signaling a stable but non-evolving codebase.