Skip to content

Commit e71dd4a

Browse files
committed
Fix title depth
1 parent 6e67986 commit e71dd4a

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

blog_professional/_posts/2021-03-30-include-python.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ date: 2021-03-30
55
no_toc: true
66
---
77

8-
# The Problem
8+
## The Problem
99

1010
You wrote a beautiful lil' Python script.
1111
:snake:
@@ -25,7 +25,7 @@ Wanting to embed data into C++ source is a common-enough concern that there are
2525
We could [use `xxd`](https://stackoverflow.com/a/411000) to generate a header with the script inside a `unsigned char[]`, but keeping that autogenerated header in sync with the script source would complicate our build process.
2626
There's some [finagling in the standards committee](http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2018/p1040r0.html) that might eventually make this problem less annoying, but at best that's a ways off.
2727

28-
# The Solution
28+
## The Solution
2929

3030
Turns out that Python also has raw string literal syntax.
3131
Conveniently, these strings also start out with `R"`.
@@ -42,7 +42,7 @@ Indeed, Python will happily ignore any loose strings, say, you might happen to p
4242

4343
See where this is going?
4444

45-
# The Abomination
45+
## The Abomination
4646

4747
We're going to shove the C++ raw string literal syntax *into* our python script and then `#include` that.
4848

0 commit comments

Comments
 (0)