-
-
Notifications
You must be signed in to change notification settings - Fork 507
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Jedi News/Updates (Please Subscribe) #1063
Comments
So let's start: I'd like you to comment on how Virtualenvs and different Python versions should be handled. I'm very interested in feedback on the API. Please let me know if there are things that could be improved. Otherwise you will be stuck with a bad API that you might not want ;-) This will be released as part of Jedi 0.12.0 in a few weeks. So hurry up and comment! The release notes will look like this for 0.12.0:
|
Just released: Jedi 0.12.0 (2018-04-15)
|
Jedi 0.13.0 (2018-10-02)
|
Jedi 0.13.2 (2018-12-15)
This issue was pretty bad. Please upgrade! |
Released parso
|
Released parso 0.3.3. This is not a Jedi upgrade, but a small follow up (one relevant bugfix for Jedi). Please upgrade, especially if you are using 0.3.2. Parso 0.3.3 (2018-02-06)
|
Jedi 0.13.3 (2019-02-24)
Upgrade is recommended mostly if you are using Jedi with embedded Python (this means e.g. embedded inside VIM). This bug also affected only Windows/Mac and not Linux/BSD. BTW: Upgrading parso to latest is also recommended. |
Jedi 0.14.0 (2019-06-20)
You can also follow me on twitter to get these kinds of news: https://twitter.com/jedidjah_ch/ (I don't spam). |
Jedi 0.14.1 (2019-07-13)
Parso 0.5.1 (2019-07-13)
|
Jedi 0.15.0 (2019-08-11)
New APIs:
|
0.15.2 (2019-12-20)Upgrade needs a parso upgrade.
|
0.16.0 (2020-01-26)
|
Released parso 0.7.0. This is not a Jedi upgrade.This should be backwards compatible with the last few Jedi versions, so please just upgrade. The upgrade helps a lot with some situations where after working with some code completions would stop. This was completely not reproducible (or it was very hard to reproduce), so people never really reported it. I fixed a lot of annoying bugs in the diff parser. The fuzzer finally and for the first time did not find issues anymore even after running it for more than 24 hours (500k tests). |
0.17.0 (2020-04-14)
This is likely going to be the last minor version that supports Python 2 and |
0.17.1 (2020-06-20)
|
0.17.2 (2020-07-17)
This will be the last release that supports Python 2 and Python 3.5. |
I am switching to a mailing list instead of this issue. Please write an empty email to I might post the next few updates here as well, but the mailing list will be where the releases will be announced in the future. |
To make it easier for people to stay in touch what's changing in jedi, I made this thread. I'm not going to post here often and there will comments are blocked. This thread is about summarizing things that you can comment on in separate issues.
Feel free to subscribe and unsubscribe as you want. There should be a button on the right side where you can turn notifications on and off.
cc'd a few people that might be interested:
@blueyed @dbrgn @tkf @mfussenegger @Alexey-T @sadovnychyi @scribu @jorgenschaefer @takluyver @Valloric @vheon @micbou @asmeurer @Shougo @zchee @maralla @proofit404 @syohex @immerrr @srusskih @DamnWidget @lawrenceakka @brennv @abe33 @patrys @wolph @isamert @Kozea @DonJayamanne @brettcannon @MikhailArkhipov @Carreau
The text was updated successfully, but these errors were encountered: