5 3 Why django CMS? 7 4 Software version requirements and release notes 9 4.1 Django/Python compatibility table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Python Module VERSION REQUIREMENTS AND RELEASE NOTES This document refers to version 3.10.0. 4.1 Django/Python compatibility table LTS in the table indicates a combination of Django and django CMS both covered by a long-term newer, and Python 2.7 or 3.3 or newer. This tutorial assumes you are using Python 3. You can find compatibility table for particular python version here Your working environment We’re going to assume that you

5 3 Why django CMS? 7 4 Software version requirements and release notes 9 4.1 Django/Python compatibility table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Python Module VERSION REQUIREMENTS AND RELEASE NOTES This document refers to version 3.9.0. 4.1 Django/Python compatibility table LTS in the table indicates a combination of Django and django CMS both covered by a long-term browser, where you should be invited to login, and then create a new page. 4.1. Django/Python compatibility table 11 django cms Documentation, Release 3.9.0 Congratulations, you now have installed a fully

http_client = AsyncHTTPClient() response = await http_client.fetch(url) return response.body Or for compatibility with older versions of Python, using the tornado.gen module: 14 Chapter 6. DocumentationTornado and await keywords (functions using these keywords are also called “native corou- tines”). For compatibility with older versions of Python, you can use “decorated” or “yield-based” coroutines using the tornado Native coroutines are the recommended form whenever possible. Only use decorated coroutines when compatibility with older versions of Python is required. Examples in the Tornado documentation will generally

ninja: build stopped: subcommand failed.Packaging BMIs - cont’d New dimension of complexity: BMI compatibility We may be binary/ABI compatible with the symbols in the library (.a/.so) But our sources are msvc: /ifcOnlyPackaging the module interface (cont’d) ● All BMIs generated locally, increasing compatibility ○ Same compiler and compiler version as the translation units doing the importing ○ Module interface static) Module onlyBMI compatibility fmt.cc Packaged module library -std=c++20BMI compatibility fmt.cc Packaged module library fmt.pcm fmt.o -std=c++20BMI compatibility fmt.cc libfmt.a Packaged

AsyncHTTPClient() response = await http_client.fetch(url) return response.body Or for compatibility with older versions of Python, using the tornado.gen module: from tornado.httpclient import AsyncHTTPClient and await keywords (functions using these keywords are also called “native coroutines”). For compatibility with older versions of Python, you can use “decorated” or “yield-based” coroutines using the tornado Native coroutines are the recommended form whenever possible. Only use decorated coroutines when compatibility with older versions of Python is required. Examples in the Tornado documentation will generally

through generalization Compatibility for C++ Why • What kind • What plan3 green-field language invent new idioms/styles new modules new ecosystem/packagers compatibility bridges refresh C++ itself make C++ guidance default make C++ modules default keep C++ ecosystem/packagers keep C++ compatibility this talk4 What could we do if we had a cleanly demarcated “bubble of new code,” via directly, no wrapping/marshaling/thunking/… Easily adoptable 100% binary compatibility always 100% source compatibility always available, but “zero-overhead” (only pay for it if you use it)

certain device cate- gories. For details, see chapter 3.10.1, USB settings, page 53. – Hardware compatibility. VirtualBox virtualizes a vast array of virtual devices, among them many devices that are typically devices, not based on any physical counterpart. It is a simple, synthetic device which provides compatibility with standard VGA and several extended registers used by the VESA BIOS Extensions (VBE). • Storage would be enough for VirtualBox by itself, this mul- titude of storage adapters is required for compatibility with other hypervisors. Windows is particularly picky about its boot devices, and migrating VMs

Performance > Compatibility. // Now, it's important to note that we're working under certain assumptions and have made some trade- offs. Specifically, we've chosen to sacrifice some compatibility in favor industry, servers are typically homogeneous, which allows us to make certain assumptions about compatibility. // These design choices reflect our focus on maximizing performance for specific use cases, particularly performance outweigh the need for broad compatibility. • However, we're not entirely disregarding compatibility. We have some attempts to address compatibility issues, which we'll discuss later in the

3.2 March 2024 3.8.x October 2020 2.2 March 2022 3.7.x June 2020 2.2 March 2022 Django/Python compatibility table LTS in the table indicates a combination of Django and django CMS both covered by a long-term pluginmodel.CMSPlugin. While the use of CMSPlugin.page is deprecated the property still exists as a compatibility shim. Handling Relations Some user interactions make it necessary to create a copy of the plugin triggered. The cms-content-refresh jQuery event on the window is also triggered for backwards compatibility. Some plugins might need to run a certain bit of javascript after a content refresh. This is why

certain device cate- gories. For details, see chapter 3.10.1, USB settings, page 56. – Hardware compatibility. VirtualBox virtualizes a vast array of virtual devices, among them many devices that are typically devices, not based on any physical counterpart. It is a simple, synthetic device which provides compatibility with standard VGA and several extended registers used by the VESA BIOS Extensions (VBE). • Storage would be enough for VirtualBox by itself, this mul- titude of storage adapters is required for compatibility with other hypervisors. Windows is particularly picky about its boot devices, and migrating VMs