Mercurial > vim
view runtime/keymap/bulgarian-bds.vim @ 32936:c517845bd10e v9.0.1776
patch 9.0.1776: No support for stable Python 3 ABI
Commit: https://github.com/vim/vim/commit/c13b3d1350b60b94fe87f0761ea31c0e7fb6ebf3
Author: Yee Cheng Chin <ychin.git@gmail.com>
Date: Sun Aug 20 21:18:38 2023 +0200
patch 9.0.1776: No support for stable Python 3 ABI
Problem: No support for stable Python 3 ABI
Solution: Support Python 3 stable ABI
Commits:
1) Support Python 3 stable ABI to allow mixed version interoperatbility
Vim currently supports embedding Python for use with plugins, and the
"dynamic" linking option allows the user to specify a locally installed
version of Python by setting `pythonthreedll`. However, one caveat is
that the Python 3 libs are not binary compatible across minor versions,
and mixing versions can potentially be dangerous (e.g. let's say Vim was
linked against the Python 3.10 SDK, but the user sets `pythonthreedll`
to a 3.11 lib). Usually, nothing bad happens, but in theory this could
lead to crashes, memory corruption, and other unpredictable behaviors.
It's also difficult for the user to tell something is wrong because Vim
has no way of reporting what Python 3 version Vim was linked with.
For Vim installed via a package manager, this usually isn't an issue
because all the dependencies would already be figured out. For prebuilt
Vim binaries like MacVim (my motivation for working on this), AppImage,
and Win32 installer this could potentially be an issue as usually a
single binary is distributed. This is more tricky when a new Python
version is released, as there's a chicken-and-egg issue with deciding
what Python version to build against and hard to keep in sync when a new
Python version just drops and we have a mix of users of different Python
versions, and a user just blindly upgrading to a new Python could lead to
bad interactions with Vim.
Python 3 does have a solution for this problem: stable ABI / limited API
(see https://docs.python.org/3/c-api/stable.html). The C SDK limits the
API to a set of functions that are promised to be stable across
versions. This pull request adds an ifdef config that allows us to turn
it on when building Vim. Vim binaries built with this option should be
safe to freely link with any Python 3 libraies without having the
constraint of having to use the same minor version.
Note: Python 2 has no such concept and this doesn't change how Python 2
integration works (not that there is going to be a new version of Python
2 that would cause compatibility issues in the future anyway).
---
Technical details:
======
The stable ABI can be accessed when we compile with the Python 3 limited
API (by defining `Py_LIMITED_API`). The Python 3 code (in `if_python3.c`
and `if_py_both.h`) would now handle this and switch to limited API
mode. Without it set, Vim will still use the full API as before so this
is an opt-in change.
The main difference is that `PyType_Object` is now an opaque struct that
we can't directly create "static types" out of, and we have to create
type objects as "heap types" instead. This is because the struct is not
stable and changes from version to version (e.g. 3.8 added a
`tp_vectorcall` field to it). I had to change all the types to be
allocated on the heap instead with just a pointer to them.
Other functions are also simply missing in limited API, or they are
introduced too late (e.g. `PyUnicode_AsUTF8AndSize` in 3.10) to it that
we need some other ways to do the same thing, so I had to abstract a few
things into macros, and sometimes re-implement functions like
`PyObject_NEW`.
One caveat is that in limited API, `OutputType` (used for replacing
`sys.stdout`) no longer inherits from `PyStdPrinter_Type` which I don't
think has any real issue other than minor differences in how they
convert to a string and missing a couple functions like `mode()` and
`fileno()`.
Also fixed an existing bug where `tp_basicsize` was set incorrectly for
`BufferObject`, `TabListObject, `WinListObject`.
Technically, there could be a small performance drop, there is a little
more indirection with accessing type objects, and some APIs like
`PyUnicode_AsUTF8AndSize` are missing, but in practice I didn't see any
difference, and any well-written Python plugin should try to avoid
excessing callbacks to the `vim` module in Python anyway.
I only tested limited API mode down to Python 3.7, which seemes to
compile and work fine. I haven't tried earlier Python versions.
2) Fix PyIter_Check on older Python vers / type##Ptr unused warning
For PyIter_Check, older versions exposed them as either macros (used in
full API), or a function (for use in limited API). A previous change
exposed PyIter_Check to the dynamic build because Python just moved it
to function-only in 3.10 anyway. Because of that, just make sure we
always grab the function in dynamic builds in earlier versions since
that's what Python eventually did anyway.
3) Move Py_LIMITED_API define to configure script
Can now use --with-python-stable-abi flag to customize what stable ABI
version to target. Can also use an env var to do so as well.
4) Show +python/dyn-stable in :version, and allow has() feature query
Not sure if the "/dyn-stable" suffix would break things, or whether we
should do it another way. Or just don't show it in version and rely on
has() feature checking.
5) Documentation first draft. Still need to implement v:python3_version
6) Fix PyIter_Check build breaks when compiling against Python 3.8
7) Add CI coverage stable ABI on Linux/Windows / make configurable on Windows
This adds configurable options for Windows make files (both MinGW and
MSVC). CI will also now exercise both traditional full API and stable
ABI for Linux and Windows in the matrix for coverage.
Also added a "dynamic" option to Linux matrix as a drive-by change to
make other scripting languages like Ruby / Perl testable under both
static and dynamic builds.
8) Fix inaccuracy in Windows docs
Python's own docs are confusing but you don't actually want to use
`python3.dll` for the dynamic linkage.
9) Add generated autoconf file
10) Add v:python3_version support
This variable indicates the version of Python3 that Vim was built
against (PY_VERSION_HEX), and will be useful to check whether the Python
library you are loading in dynamically actually fits it. When built with
stable ABI, it will be the limited ABI version instead
(`Py_LIMITED_API`), which indicates the minimum version of Python 3 the
user should have, rather than the exact match. When stable ABI is used,
we won't be exposing PY_VERSION_HEX in this var because it just doesn't
seem necessary to do so (the whole point of stable ABI is the promise
that it will work across versions), and I don't want to confuse the user
with too many variables.
Also, cleaned up some documentation, and added help tags.
11) Fix Python 3.7 compat issues
Fix a couple issues when using limited API < 3.8
- Crash on exit: In Python 3.7, if a heap-allocated type is destroyed
before all instances are, it would cause a crash later. This happens
when we destroyed `OptionsType` before calling `Py_Finalize` when
using the limited API. To make it worse, later versions changed the
semantics and now each instance has a strong reference to its own type
and the recommendation has changed to have each instance de-ref its
own type and have its type in GC traversal. To avoid dealing with
these cross-version variations, we just don't free the heap type. They
are static types in non-limited-API anyway and are designed to last
through the entirety of the app, and we also don't restart the Python
runtime and therefore do not need it to have absolutely 0 leaks.
See:
- https://docs.python.org/3/whatsnew/3.8.html#changes-in-the-c-api
- https://docs.python.org/3/whatsnew/3.9.html#changes-in-the-c-api
- PyIter_Check: This function is not provided in limited APIs older than
3.8. Previously I was trying to mock it out using manual
PyType_GetSlot() but it was brittle and also does not actually work
properly for static types (it will generate a Python error). Just
return false. It does mean using limited API < 3.8 is not recommended
as you lose the functionality to handle iterators, but from playing
with plugins I couldn't find it to be an issue.
- Fix loading of PyIter_Check so it will be done when limited API < 3.8.
Otherwise loading a 3.7 Python lib will fail even if limited API was
specified to use it.
12) Make sure to only load `PyUnicode_AsUTF8AndSize` in needed in limited API
We don't use this function unless limited API >= 3.10, but we were
loading it regardless. Usually it's ok in Unix-like systems where Python
just has a single lib that we load from, but in Windows where there is a
separate python3.dll this would not work as the symbol would not have
been exposed in this more limited DLL file. This makes it much clearer
under what condition is this function needed.
closes: #12032
Signed-off-by: Christian Brabandt <cb@256bit.org>
Co-authored-by: Yee Cheng Chin <ychin.git@gmail.com>
author | Christian Brabandt <cb@256bit.org> |
---|---|
date | Sun, 20 Aug 2023 21:30:04 +0200 |
parents | b9e314fe473f |
children |
line wrap: on
line source
" Vim keymap file for Bulgarian and Russian characters, "bds" layout. " Most of it can be used with both utf-8 and cp1251 file encodings, except " the accented characters which can only be stored in utf-8. " This file itself is in utf-8. " Maintainer: Boyko Bantchev <boykobb@gmail.com> " URI: http://www.math.bas.bg/bantchev/vim/bulgarian-bds.vim " Last Changed: 2010 May 4 " This keymap corresponds to what is called Bulgarian standard typewriter " keyboard layout, or "БДС". " " Note that, in addition to the Bulgarian alphabet, the BDS layout prescribes " the presence of the following characters: " — The Russian letters ы (small), and Э and э (capital and small). " — The latin capital letters I and V – used to type Roman numerals " without having to leave Cyrillic mode. " " Some punctuation characters present in ascii are mapped in BDS to keys " different from the ones they occupy in the QWERTY layout, because the latter " keys are used to type other characters. " " In this keymap, also defined (besides BDS) are: " — The Russian letters Ё and ё (capital and small), as well as the " Russian capital letter Ы (see above for the small counterpart). " This way, using the bulgarian-bds keymap, one can access both " the Bulgarian and the Russian alphabets. " — The quotation marks „ “ ” ‘ ’ (used in the Bulgarian and English " quotation styles), as well as « » (Russian quotation style). " — The characters §, №, – (en-dash), — (em-dash), …, •, ·, ±, °, ¬, " ¤, €, ‰, †, ‡, and ¶. " " The keymap also defines key combinations for grave and acute accents. " (Grave accent is used in Bulgarian, acute in Russian, but both accents " apply to other languages as well.) " " For details of what key or key combination maps to what character, please " see below the map itself. " " See also http://www.math.bas.bg/bantchev/vim/kbdbul.html (in Bulgarian). scriptencoding utf-8 let b:keymap_name = "bds" loadkeymap D А CYRILLIC CAPITAL LETTER A ? Б CYRILLIC CAPITAL LETTER BE L В CYRILLIC CAPITAL LETTER VE H Г CYRILLIC CAPITAL LETTER GHE O Д CYRILLIC CAPITAL LETTER DE E Е CYRILLIC CAPITAL LETTER IE E:: Ё CYRILLIC CAPITAL LETTER IO G Ж CYRILLIC CAPITAL LETTER ZHE P З CYRILLIC CAPITAL LETTER ZE R И CYRILLIC CAPITAL LETTER I X Й CYRILLIC CAPITAL LETTER SHORT I U К CYRILLIC CAPITAL LETTER KA > Л CYRILLIC CAPITAL LETTER EL : М CYRILLIC CAPITAL LETTER EM K Н CYRILLIC CAPITAL LETTER EN F О CYRILLIC CAPITAL LETTER O M П CYRILLIC CAPITAL LETTER PE < Р CYRILLIC CAPITAL LETTER ER I С CYRILLIC CAPITAL LETTER ES J Т CYRILLIC CAPITAL LETTER TE W У CYRILLIC CAPITAL LETTER U B Ф CYRILLIC CAPITAL LETTER EF N Х CYRILLIC CAPITAL LETTER HA { Ц CYRILLIC CAPITAL LETTER TSE \" Ч CYRILLIC CAPITAL LETTER CHE T Ш CYRILLIC CAPITAL LETTER SHA Y Щ CYRILLIC CAPITAL LETTER SHCHA C Ъ CYRILLIC CAPITAL LETTER HARD SIGN CX Ы CYRILLIC CAPITAL LETTER YERU A Ь CYRILLIC CAPITAL LETTER SOFT SIGN V Э CYRILLIC CAPITAL LETTER REVERSED E Z Ю CYRILLIC CAPITAL LETTER YU S Я CYRILLIC CAPITAL LETTER YA d а CYRILLIC SMALL LETTER A \/ б CYRILLIC SMALL LETTER BE l в CYRILLIC SMALL LETTER VE h г CYRILLIC SMALL LETTER GHE o д CYRILLIC SMALL LETTER DE e е CYRILLIC SMALL LETTER IE e:: ё CYRILLIC SMALL LETTER IO g ж CYRILLIC SMALL LETTER ZHE p з CYRILLIC SMALL LETTER ZE r и CYRILLIC SMALL LETTER I x й CYRILLIC SMALL LETTER SHORT I u к CYRILLIC SMALL LETTER KA \. л CYRILLIC SMALL LETTER EL ; м CYRILLIC SMALL LETTER EM k н CYRILLIC SMALL LETTER EN f о CYRILLIC SMALL LETTER O m п CYRILLIC SMALL LETTER PE , р CYRILLIC SMALL LETTER ER i с CYRILLIC SMALL LETTER ES j т CYRILLIC SMALL LETTER TE w у CYRILLIC SMALL LETTER U b ф CYRILLIC SMALL LETTER EF n х CYRILLIC SMALL LETTER HA [ ц CYRILLIC SMALL LETTER TSE ' ч CYRILLIC SMALL LETTER CHE t ш CYRILLIC SMALL LETTER SHA y щ CYRILLIC SMALL LETTER SHCHA c ъ CYRILLIC SMALL LETTER HARD SIGN Q ы CYRILLIC SMALL LETTER YERU a ь CYRILLIC SMALL LETTER SOFT SIGN v э CYRILLIC SMALL LETTER REVERSED E z ю CYRILLIC SMALL LETTER YU s я CYRILLIC SMALL LETTER YA _ I LATIN CAPITAL LETTER I + V LATIN CAPITAL LETTER V $ " QUOTATION MARK \\ ( LEFT PARENTHESIS | ) RIGHT PARENTHESIS # + PLUS SIGN q , COMMA ( - HYPHEN-MINUS = . FULL STOP (PERIOD) * / SOLIDUS (SLASH) & : COLON ] ; SEMICOLON ^ = EQUALS SIGN @ ? QUESTION MARK } § SECTION SIGN (PARAGRAPH SIGN) ) № NUMERO SIGN -- – EN DASH --- — EM DASH .. … HORIZONTAL ELLIPSIS `` “ LEFT DOUBLE QUOTATION MARK '' ” RIGHT DOUBLE QUOTATION MARK ,, „ DOUBLE LOW-9 QUOTATION MARK `. ‘ LEFT SINGLE QUOTATION MARK '. ’ RIGHT SINGLE QUOTATION MARK << « LEFT-POINTING DOUBLE ANGLE QUOTATION MARK >> » RIGHT-POINTING DOUBLE ANGLE QUOTATION MARK ** • BULLET ,. · MIDDLE DOT +- ± PLUS-MINUS SIGN ^o ° DEGREE SIGN ~~ ¬ NOT SIGN @@ ¤ CURRENCY SIGN $$ € EURO SIGN %% ‰ PER MILLE SIGN +| † DAGGER ++ ‡ DOUBLE DAGGER || ¶ PILCROW SIGN " Accented characters cannot map onto cp1251 – use utf-8 file encoding. " To apply an accent to a letter, type the corresponding key combination " to the immediate right of that letter. ^` <char-0x300> COMBINING GRAVE ACCENT ^' <char-0x301> COMBINING ACUTE ACCENT