In [144]: ser = pd.Series(arr[:, 0])\n \n In [145]: %timeit ser.iloc[indexer]\n .....: %timeit ser.take(indexer)\n .....: \n-151 us +- 1.51 us per loop (mean +- std. dev. of 7 runs, 10,000 loops each)\n-124 us +- 2.66 us per loop (mean +- std. dev. of 7 runs, 10,000 loops each)\n+150 us +- 2.3 us per loop (mean +- std. dev. of 7 runs, 10,000 loops each)\n+121 us +- 1.05 us per loop (mean +- std. dev. of 7 runs, 10,000 loops each)\n We have discussed MultiIndex in the previous sections pretty extensively.\n Documentation about DatetimeIndex and PeriodIndex are shown here,\n", "details": [{"source1": "html2text {}", "source2": "html2text {}", "unified_diff": "@@ -1245,23 +1245,23 @@\n In [141]: indexer = np.arange(10000)\n \n In [142]: random.shuffle(indexer)\n \n In [143]: %timeit arr[indexer]\n .....: %timeit arr.take(indexer, axis=0)\n .....:\n-196 us +- 1.28 us per loop (mean +- std. dev. of 7 runs, 10,000 loops each)\n-89 us +- 400 ns per loop (mean +- std. dev. of 7 runs, 10,000 loops each)\n+193 us +- 1.42 us per loop (mean +- std. dev. of 7 runs, 10,000 loops each)\n+91.9 us +- 228 ns per loop (mean +- std. dev. of 7 runs, 10,000 loops each)\n In [144]: ser = pd.Series(arr[:, 0])\n \n In [145]: %timeit ser.iloc[indexer]\n .....: %timeit ser.take(indexer)\n .....:\n-151 us +- 1.51 us per loop (mean +- std. dev. of 7 runs, 10,000 loops each)\n-124 us +- 2.66 us per loop (mean +- std. dev. of 7 runs, 10,000 loops each)\n+150 us +- 2.3 us per loop (mean +- std. dev. of 7 runs, 10,000 loops each)\n+121 us +- 1.05 us per loop (mean +- std. dev. of 7 runs, 10,000 loops each)\n *\b**\b**\b**\b**\b* I\bIn\bnd\bde\bex\bx t\bty\byp\bpe\bes\bs_\b#\b# *\b**\b**\b**\b**\b*\n We have discussed MultiIndex in the previous sections pretty extensively.\n Documentation about DatetimeIndex and PeriodIndex are shown _\bh_\be_\br_\be, and\n documentation about TimedeltaIndex is found _\bh_\be_\br_\be.\n In the following sub-sections we will highlight some other index types.\n *\b**\b**\b**\b* C\bCa\bat\bte\beg\bgo\bor\bri\bic\bca\bal\blI\bIn\bnd\bde\bex\bx_\b#\b# *\b**\b**\b**\b*\n _\bC_\ba_\bt_\be_\bg_\bo_\br_\bi_\bc_\ba_\bl_\bI_\bn_\bd_\be_\bx is a type of index that is useful for supporting indexing with\n"}]}, {"source1": "./usr/share/doc/python-pandas-doc/html/user_guide/enhancingperf.html", "source2": "./usr/share/doc/python-pandas-doc/html/user_guide/enhancingperf.html", "unified_diff": "@@ -592,31 +592,31 @@\n ...: s += f(a + i * dx)\n ...: return s * dx\n ...: \n \n \n
We achieve our result by using DataFrame.apply() (row-wise):
In [5]: %timeit df.apply(lambda x: integrate_f(x["a"], x["b"], x["N"]), axis=1)\n-71 ms +- 2.76 ms per loop (mean +- std. dev. of 7 runs, 10 loops each)\n+73.7 ms +- 9.68 ms per loop (mean +- std. dev. of 7 runs, 10 loops each)\n Let\u2019s take a look and see where the time is spent during this operation\n using the prun ipython magic function:
\n# most time consuming 4 calls\n In [6]: %prun -l 4 df.apply(lambda x: integrate_f(x["a"], x["b"], x["N"]), axis=1) # noqa E999\n- 605946 function calls (605928 primitive calls) in 0.218 seconds\n+ 605946 function calls (605928 primitive calls) in 0.407 seconds\n \n Ordered by: internal time\n List reduced from 159 to 4 due to restriction <4>\n \n ncalls tottime percall cumtime percall filename:lineno(function)\n- 1000 0.132 0.000 0.191 0.000 <ipython-input-4-c2a74e076cf0>:1(integrate_f)\n- 552423 0.058 0.000 0.058 0.000 <ipython-input-3-c138bdd570e3>:1(f)\n- 3000 0.004 0.000 0.017 0.000 series.py:1095(__getitem__)\n- 3000 0.003 0.000 0.008 0.000 series.py:1220(_get_value)\n+ 1000 0.220 0.000 0.335 0.000 <ipython-input-4-c2a74e076cf0>:1(integrate_f)\n+ 552423 0.115 0.000 0.115 0.000 <ipython-input-3-c138bdd570e3>:1(f)\n+ 3000 0.019 0.000 0.040 0.000 series.py:1220(_get_value)\n+ 3000 0.011 0.000 0.011 0.000 base.py:3777(get_loc)\n By far the majority of time is spend inside either integrate_f or f,\n hence we\u2019ll concentrate our efforts cythonizing these two functions.
In [9]: %timeit df.apply(lambda x: integrate_f_plain(x["a"], x["b"], x["N"]), axis=1)\n-73.9 ms +- 269 us per loop (mean +- std. dev. of 7 runs, 10 loops each)\n+71 ms +- 34.8 us per loop (mean +- std. dev. of 7 runs, 10 loops each)\n This has improved the performance compared to the pure Python approach by one-third.
\nWe can annotate the function variables and return types as well as use cdef\n@@ -658,15 +658,15 @@\n ....: for i in range(N):\n ....: s += f_typed(a + i * dx)\n ....: return s * dx\n ....: \n \n \n
In [11]: %timeit df.apply(lambda x: integrate_f_typed(x["a"], x["b"], x["N"]), axis=1)\n-8.72 ms +- 44.8 us per loop (mean +- std. dev. of 7 runs, 100 loops each)\n+8.61 ms +- 78.6 us per loop (mean +- std. dev. of 7 runs, 100 loops each)\n Annotating the functions with C types yields an over ten times performance improvement compared to\n the original Python implementation.
\nIn [13]: %%cython\n ....: cimport numpy as np\n ....: import numpy as np\n ....: cdef double f_typed(double x) except? -2:\n ....: return x * (x - 1)\n@@ -722,15 +722,15 @@\n This implementation creates an array of zeros and inserts the result\n of integrate_f_typed applied over each row. Looping over an ndarray is faster\n in Cython than looping over a Series object.
Since apply_integrate_f is typed to accept an np.ndarray, Series.to_numpy()\n calls are needed to utilize this function.
In [14]: %timeit apply_integrate_f(df["a"].to_numpy(), df["b"].to_numpy(), df["N"].to_numpy())\n-1.17 ms +- 215 ns per loop (mean +- std. dev. of 7 runs, 1,000 loops each)\n+1.16 ms +- 519 ns per loop (mean +- std. dev. of 7 runs, 1,000 loops each)\n Performance has improved from the prior implementation by almost ten times.
\n \nThe majority of the time is now spent in apply_integrate_f. Disabling Cython\u2019s boundscheck\n@@ -782,15 +782,15 @@\n from /build/reproducible-path/pandas-2.2.3+dfsg/buildtmp/.cache/ipython/cython/_cython_magic_883da8958ecc60be73b28b7124368f9c7cc2d174.c:1251:\n /usr/lib/aarch64-linux-gnu/python3-numpy/numpy/_core/include/numpy/npy_1_7_deprecated_api.h:17:2: warning: #warning "Using deprecated NumPy API, disable it with " "#define NPY_NO_DEPRECATED_API NPY_1_7_API_VERSION" [-Wcpp]\n 17 | #warning "Using deprecated NumPy API, disable it with " \\\n | ^~~~~~~\n
In [17]: %timeit apply_integrate_f_wrap(df["a"].to_numpy(), df["b"].to_numpy(), df["N"].to_numpy())\n-813 us +- 191 ns per loop (mean +- std. dev. of 7 runs, 1,000 loops each)\n+814 us +- 273 ns per loop (mean +- std. dev. of 7 runs, 1,000 loops each)\n However, a loop indexer i accessing an invalid location in an array would cause a segfault because memory access isn\u2019t checked.\n For more about boundscheck and wraparound, see the Cython docs on\n compiler directives.
DataFrame. This engine requires the\n optional dependency numexpr to be installed.\n The 'python' engine is generally not useful except for testing\n other evaluation engines against it. You will achieve no performance\n benefits using eval() with engine='python' and may\n incur a performance hit.
In [40]: %timeit df1 + df2 + df3 + df4\n-8.5 ms +- 139 us per loop (mean +- std. dev. of 7 runs, 100 loops each)\n+8.51 ms +- 61.6 us per loop (mean +- std. dev. of 7 runs, 100 loops each)\n In [41]: %timeit pd.eval("df1 + df2 + df3 + df4", engine="python")\n-10.9 ms +- 62.2 us per loop (mean +- std. dev. of 7 runs, 100 loops each)\n+11 ms +- 167 us per loop (mean +- std. dev. of 7 runs, 100 loops each)\n DataFrame.eval() method#In addition to the top level pandas.eval() function you can also\n evaluate an expression in the \u201ccontext\u201d of a DataFrame.
In [58]: nrows, ncols = 20000, 100\n \n In [59]: df1, df2, df3, df4 = [pd.DataFrame(np.random.randn(nrows, ncols)) for _ in range(4)]\n DataFrame arithmetic:
In [60]: %timeit df1 + df2 + df3 + df4\n-8.54 ms +- 372 us per loop (mean +- std. dev. of 7 runs, 100 loops each)\n+8.21 ms +- 164 us per loop (mean +- std. dev. of 7 runs, 100 loops each)\n In [61]: %timeit pd.eval("df1 + df2 + df3 + df4")\n-7.36 ms +- 434 us per loop (mean +- std. dev. of 7 runs, 100 loops each)\n+6.94 ms +- 67.2 us per loop (mean +- std. dev. of 7 runs, 100 loops each)\n DataFrame comparison:
In [62]: %timeit (df1 > 0) & (df2 > 0) & (df3 > 0) & (df4 > 0)\n-10.8 ms +- 97.4 us per loop (mean +- std. dev. of 7 runs, 100 loops each)\n+10.6 ms +- 127 us per loop (mean +- std. dev. of 7 runs, 100 loops each)\n In [63]: %timeit pd.eval("(df1 > 0) & (df2 > 0) & (df3 > 0) & (df4 > 0)")\n-12.2 ms +- 230 us per loop (mean +- std. dev. of 7 runs, 100 loops each)\n+11.8 ms +- 155 us per loop (mean +- std. dev. of 7 runs, 100 loops each)\n DataFrame arithmetic with unaligned axes.
In [64]: s = pd.Series(np.random.randn(50))\n \n In [65]: %timeit df1 + df2 + df3 + df4 + s\n-19.5 ms +- 94.6 us per loop (mean +- std. dev. of 7 runs, 100 loops each)\n+19.8 ms +- 73 us per loop (mean +- std. dev. of 7 runs, 100 loops each)\n In [66]: %timeit pd.eval("df1 + df2 + df3 + df4 + s")\n-9.5 ms +- 131 us per loop (mean +- std. dev. of 7 runs, 100 loops each)\n+8.54 ms +- 45 us per loop (mean +- std. dev. of 7 runs, 100 loops each)\n Note
\nOperations such as
\n1 and 2 # would parse to 1 & 2, but should evaluate to 2\n 3 or 4 # would parse to 3 | 4, but should evaluate to 3\n", "details": [{"source1": "html2text {}", "source2": "html2text {}", "unified_diff": "@@ -110,32 +110,32 @@\n ...: dx = (b - a) / N\n ...: for i in range(N):\n ...: s += f(a + i * dx)\n ...: return s * dx\n ...:\n We achieve our result by using _\bD_\ba_\bt_\ba_\bF_\br_\ba_\bm_\be_\b._\ba_\bp_\bp_\bl_\by_\b(_\b) (row-wise):\n In [5]: %timeit df.apply(lambda x: integrate_f(x[\"a\"], x[\"b\"], x[\"N\"]), axis=1)\n-71 ms +- 2.76 ms per loop (mean +- std. dev. of 7 runs, 10 loops each)\n+73.7 ms +- 9.68 ms per loop (mean +- std. dev. of 7 runs, 10 loops each)\n Let\u2019s take a look and see where the time is spent during this operation using\n the _\bp_\br_\bu_\bn_\b _\bi_\bp_\by_\bt_\bh_\bo_\bn_\b _\bm_\ba_\bg_\bi_\bc_\b _\bf_\bu_\bn_\bc_\bt_\bi_\bo_\bn:\n # most time consuming 4 calls\n In [6]: %prun -l 4 df.apply(lambda x: integrate_f(x[\"a\"], x[\"b\"], x[\"N\"]),\n axis=1) # noqa E999\n- 605946 function calls (605928 primitive calls) in 0.218 seconds\n+ 605946 function calls (605928 primitive calls) in 0.407 seconds\n \n Ordered by: internal time\n List reduced from 159 to 4 due to restriction <4>\n \n ncalls tottime percall cumtime percall filename:lineno(function)\n- 1000 0.132 0.000 0.191 0.000 :1\n+ 1000 0.220 0.000 0.335 0.000 :1\n (integrate_f)\n- 552423 0.058 0.000 0.058 0.000 :1\n+ 552423 0.115 0.000 0.115 0.000 :1\n (f)\n- 3000 0.004 0.000 0.017 0.000 series.py:1095(__getitem__)\n- 3000 0.003 0.000 0.008 0.000 series.py:1220(_get_value)\n+ 3000 0.019 0.000 0.040 0.000 series.py:1220(_get_value)\n+ 3000 0.011 0.000 0.011 0.000 base.py:3777(get_loc)\n By far the majority of time is spend inside either integrate_f or f, hence\n we\u2019ll concentrate our efforts cythonizing these two functions.\n *\b**\b**\b**\b* P\bPl\bla\bai\bin\bn C\bCy\byt\bth\bho\bon\bn_\b#\b# *\b**\b**\b**\b*\n First we\u2019re going to need to import the Cython magic function to IPython:\n In [7]: %load_ext Cython\n Now, let\u2019s simply copy our functions over to Cython:\n In [8]: %%cython\n@@ -146,15 +146,15 @@\n ...: dx = (b - a) / N\n ...: for i in range(N):\n ...: s += f_plain(a + i * dx)\n ...: return s * dx\n ...:\n In [9]: %timeit df.apply(lambda x: integrate_f_plain(x[\"a\"], x[\"b\"], x[\"N\"]),\n axis=1)\n-73.9 ms +- 269 us per loop (mean +- std. dev. of 7 runs, 10 loops each)\n+71 ms +- 34.8 us per loop (mean +- std. dev. of 7 runs, 10 loops each)\n This has improved the performance compared to the pure Python approach by one-\n third.\n *\b**\b**\b**\b* D\bDe\bec\bcl\bla\bar\bri\bin\bng\bg C\bC t\bty\byp\bpe\bes\bs_\b#\b# *\b**\b**\b**\b*\n We can annotate the function variables and return types as well as use cdef and\n cpdef to improve performance:\n In [10]: %%cython\n ....: cdef double f_typed(double x) except? -2:\n@@ -166,15 +166,15 @@\n ....: dx = (b - a) / N\n ....: for i in range(N):\n ....: s += f_typed(a + i * dx)\n ....: return s * dx\n ....:\n In [11]: %timeit df.apply(lambda x: integrate_f_typed(x[\"a\"], x[\"b\"], x[\"N\"]),\n axis=1)\n-8.72 ms +- 44.8 us per loop (mean +- std. dev. of 7 runs, 100 loops each)\n+8.61 ms +- 78.6 us per loop (mean +- std. dev. of 7 runs, 100 loops each)\n Annotating the functions with C types yields an over ten times performance\n improvement compared to the original Python implementation.\n *\b**\b**\b**\b* U\bUs\bsi\bin\bng\bg n\bnd\bda\bar\brr\bra\bay\by_\b#\b# *\b**\b**\b**\b*\n When re-profiling, time is spent creating a _\bS_\be_\br_\bi_\be_\bs from each row, and calling\n __getitem__ from both the index and the series (three times for each row).\n These Python function calls are expensive and can be improved by passing an\n np.ndarray.\n@@ -184,17 +184,17 @@\n \n Ordered by: internal time\n List reduced from 157 to 4 due to restriction <4>\n \n ncalls tottime percall cumtime percall filename:lineno(function)\n 3000 0.004 0.000 0.016 0.000 series.py:1095(__getitem__)\n 3000 0.003 0.000 0.007 0.000 series.py:1220(_get_value)\n- 3000 0.002 0.000 0.003 0.000 base.py:3777(get_loc)\n 16098 0.002 0.000 0.003 0.000 {built-in method\n builtins.isinstance}\n+ 3000 0.002 0.000 0.003 0.000 base.py:3777(get_loc)\n In [13]: %%cython\n ....: cimport numpy as np\n ....: import numpy as np\n ....: cdef double f_typed(double x) except? -2:\n ....: return x * (x - 1)\n ....: cpdef double integrate_f_typed(double a, double b, int N):\n ....: cdef int i\n@@ -235,15 +235,15 @@\n This implementation creates an array of zeros and inserts the result of\n integrate_f_typed applied over each row. Looping over an ndarray is faster in\n Cython than looping over a _\bS_\be_\br_\bi_\be_\bs object.\n Since apply_integrate_f is typed to accept an np.ndarray, _\bS_\be_\br_\bi_\be_\bs_\b._\bt_\bo_\b__\bn_\bu_\bm_\bp_\by_\b(_\b)\n calls are needed to utilize this function.\n In [14]: %timeit apply_integrate_f(df[\"a\"].to_numpy(), df[\"b\"].to_numpy(), df\n [\"N\"].to_numpy())\n-1.17 ms +- 215 ns per loop (mean +- std. dev. of 7 runs, 1,000 loops each)\n+1.16 ms +- 519 ns per loop (mean +- std. dev. of 7 runs, 1,000 loops each)\n Performance has improved from the prior implementation by almost ten times.\n *\b**\b**\b**\b* D\bDi\bis\bsa\bab\bbl\bli\bin\bng\bg c\bco\bom\bmp\bpi\bil\ble\ber\br d\bdi\bir\bre\bec\bct\bti\biv\bve\bes\bs_\b#\b# *\b**\b**\b**\b*\n The majority of the time is now spent in apply_integrate_f. Disabling Cython\u2019s\n boundscheck and wraparound checks can yield more performance.\n In [15]: %prun -l 4 apply_integrate_f(df[\"a\"].to_numpy(), df[\"b\"].to_numpy(),\n df[\"N\"].to_numpy())\n 78 function calls in 0.001 seconds\n@@ -298,15 +298,15 @@\n /usr/lib/aarch64-linux-gnu/python3-numpy/numpy/_core/include/numpy/\n npy_1_7_deprecated_api.h:17:2: warning: #warning \"Using deprecated NumPy API,\n disable it with \" \"#define NPY_NO_DEPRECATED_API NPY_1_7_API_VERSION\" [-Wcpp]\n 17 | #warning \"Using deprecated NumPy API, disable it with \" \\\n | ^~~~~~~\n In [17]: %timeit apply_integrate_f_wrap(df[\"a\"].to_numpy(), df[\"b\"].to_numpy(),\n df[\"N\"].to_numpy())\n-813 us +- 191 ns per loop (mean +- std. dev. of 7 runs, 1,000 loops each)\n+814 us +- 273 ns per loop (mean +- std. dev. of 7 runs, 1,000 loops each)\n However, a loop indexer i accessing an invalid location in an array would cause\n a segfault because memory access isn\u2019t checked. For more about boundscheck and\n wraparound, see the Cython docs on _\bc_\bo_\bm_\bp_\bi_\bl_\be_\br_\b _\bd_\bi_\br_\be_\bc_\bt_\bi_\bv_\be_\bs.\n *\b**\b**\b**\b**\b* N\bNu\bum\bmb\bba\ba (\b(J\bJI\bIT\bT c\bco\bom\bmp\bpi\bil\bla\bat\bti\bio\bon\bn)\b)_\b#\b# *\b**\b**\b**\b**\b*\n An alternative to statically compiling Cython code is to use a dynamic just-in-\n time (JIT) compiler with _\bN_\bu_\bm_\bb_\ba.\n Numba allows you to write a pure Python function which can be JIT compiled to\n@@ -609,17 +609,17 @@\n The 'numexpr' engine is the more performant engine that can yield performance\n improvements compared to standard Python syntax for large _\bD_\ba_\bt_\ba_\bF_\br_\ba_\bm_\be. This\n engine requires the optional dependency numexpr to be installed.\n The 'python' engine is generally n\bno\bot\bt useful except for testing other evaluation\n engines against it. You will achieve n\bno\bo performance benefits using _\be_\bv_\ba_\bl_\b(_\b) with\n engine='python' and may incur a performance hit.\n In [40]: %timeit df1 + df2 + df3 + df4\n-8.5 ms +- 139 us per loop (mean +- std. dev. of 7 runs, 100 loops each)\n+8.51 ms +- 61.6 us per loop (mean +- std. dev. of 7 runs, 100 loops each)\n In [41]: %timeit pd.eval(\"df1 + df2 + df3 + df4\", engine=\"python\")\n-10.9 ms +- 62.2 us per loop (mean +- std. dev. of 7 runs, 100 loops each)\n+11 ms +- 167 us per loop (mean +- std. dev. of 7 runs, 100 loops each)\n *\b**\b**\b**\b* T\bTh\bhe\be _\bD\bD_\ba\ba_\bt\bt_\ba\ba_\bF\bF_\br\br_\ba\ba_\bm\bm_\be\be_\b.\b._\be\be_\bv\bv_\ba\ba_\bl\bl_\b(\b(_\b)\b) m\bme\bet\bth\bho\bod\bd_\b#\b# *\b**\b**\b**\b*\n In addition to the top level _\bp_\ba_\bn_\bd_\ba_\bs_\b._\be_\bv_\ba_\bl_\b(_\b) function you can also evaluate an\n expression in the \u201ccontext\u201d of a _\bD_\ba_\bt_\ba_\bF_\br_\ba_\bm_\be.\n In [42]: df = pd.DataFrame(np.random.randn(5, 2), columns=[\"a\", \"b\"])\n \n In [43]: df.eval(\"a + b\")\n Out[43]:\n@@ -716,29 +716,29 @@\n _\bp_\ba_\bn_\bd_\ba_\bs_\b._\be_\bv_\ba_\bl_\b(_\b) works well with expressions containing large arrays.\n In [58]: nrows, ncols = 20000, 100\n \n In [59]: df1, df2, df3, df4 = [pd.DataFrame(np.random.randn(nrows, ncols)) for\n _ in range(4)]\n _\bD_\ba_\bt_\ba_\bF_\br_\ba_\bm_\be arithmetic:\n In [60]: %timeit df1 + df2 + df3 + df4\n-8.54 ms +- 372 us per loop (mean +- std. dev. of 7 runs, 100 loops each)\n+8.21 ms +- 164 us per loop (mean +- std. dev. of 7 runs, 100 loops each)\n In [61]: %timeit pd.eval(\"df1 + df2 + df3 + df4\")\n-7.36 ms +- 434 us per loop (mean +- std. dev. of 7 runs, 100 loops each)\n+6.94 ms +- 67.2 us per loop (mean +- std. dev. of 7 runs, 100 loops each)\n _\bD_\ba_\bt_\ba_\bF_\br_\ba_\bm_\be comparison:\n In [62]: %timeit (df1 > 0) & (df2 > 0) & (df3 > 0) & (df4 > 0)\n-10.8 ms +- 97.4 us per loop (mean +- std. dev. of 7 runs, 100 loops each)\n+10.6 ms +- 127 us per loop (mean +- std. dev. of 7 runs, 100 loops each)\n In [63]: %timeit pd.eval(\"(df1 > 0) & (df2 > 0) & (df3 > 0) & (df4 > 0)\")\n-12.2 ms +- 230 us per loop (mean +- std. dev. of 7 runs, 100 loops each)\n+11.8 ms +- 155 us per loop (mean +- std. dev. of 7 runs, 100 loops each)\n _\bD_\ba_\bt_\ba_\bF_\br_\ba_\bm_\be arithmetic with unaligned axes.\n In [64]: s = pd.Series(np.random.randn(50))\n \n In [65]: %timeit df1 + df2 + df3 + df4 + s\n-19.5 ms +- 94.6 us per loop (mean +- std. dev. of 7 runs, 100 loops each)\n+19.8 ms +- 73 us per loop (mean +- std. dev. of 7 runs, 100 loops each)\n In [66]: %timeit pd.eval(\"df1 + df2 + df3 + df4 + s\")\n-9.5 ms +- 131 us per loop (mean +- std. dev. of 7 runs, 100 loops each)\n+8.54 ms +- 45 us per loop (mean +- std. dev. of 7 runs, 100 loops each)\n Note\n Operations such as\n 1 and 2 # would parse to 1 & 2, but should evaluate to 2\n 3 or 4 # would parse to 3 | 4, but should evaluate to 3\n ~1 # this is okay, but slower when using eval\n should be performed in Python. An exception will be raised if you try to\n perform any boolean/bitwise operations with scalar operands that are not of\n"}]}, {"source1": "./usr/share/doc/python-pandas-doc/html/user_guide/scale.html", "source2": "./usr/share/doc/python-pandas-doc/html/user_guide/scale.html", "unified_diff": "@@ -1086,16 +1086,16 @@\n ....: files = pathlib.Path("data/timeseries/").glob("ts*.parquet")\n ....: counts = pd.Series(dtype=int)\n ....: for path in files:\n ....: df = pd.read_parquet(path)\n ....: counts = counts.add(df["name"].value_counts(), fill_value=0)\n ....: counts.astype(int)\n ....: \n-CPU times: user 433 us, sys: 183 us, total: 616 us\n-Wall time: 625 us\n+CPU times: user 551 us, sys: 0 ns, total: 551 us\n+Wall time: 557 us\n Out[32]: Series([], dtype: int64)\n Some readers, like pandas.read_csv(), offer parameters to control the\n chunksize when reading a single file.
Manually chunking is an OK option for workflows that don\u2019t\n require too sophisticated of operations. Some operations, like pandas.DataFrame.groupby(), are\n", "details": [{"source1": "html2text {}", "source2": "html2text {}", "unified_diff": "@@ -644,16 +644,16 @@\n ....: files = pathlib.Path(\"data/timeseries/\").glob(\"ts*.parquet\")\n ....: counts = pd.Series(dtype=int)\n ....: for path in files:\n ....: df = pd.read_parquet(path)\n ....: counts = counts.add(df[\"name\"].value_counts(), fill_value=0)\n ....: counts.astype(int)\n ....:\n-CPU times: user 433 us, sys: 183 us, total: 616 us\n-Wall time: 625 us\n+CPU times: user 551 us, sys: 0 ns, total: 551 us\n+Wall time: 557 us\n Out[32]: Series([], dtype: int64)\n Some readers, like _\bp_\ba_\bn_\bd_\ba_\bs_\b._\br_\be_\ba_\bd_\b__\bc_\bs_\bv_\b(_\b), offer parameters to control the chunksize\n when reading a single file.\n Manually chunking is an OK option for workflows that don\u2019t require too\n sophisticated of operations. Some operations, like _\bp_\ba_\bn_\bd_\ba_\bs_\b._\bD_\ba_\bt_\ba_\bF_\br_\ba_\bm_\be_\b._\bg_\br_\bo_\bu_\bp_\bb_\by_\b(_\b),\n are much harder to do chunkwise. In these cases, you may be better switching to\n a different library that implements these out-of-core algorithms for you.\n"}]}, {"source1": "./usr/share/doc/python-pandas-doc/html/user_guide/style.ipynb.gz", "source2": "./usr/share/doc/python-pandas-doc/html/user_guide/style.ipynb.gz", "unified_diff": null, "details": [{"source1": "style.ipynb", "source2": "style.ipynb", "unified_diff": null, "details": [{"source1": "Pretty-printed", "source2": "Pretty-printed", "comments": ["Similarity: 0.9985610875706213%", "Differences: {\"'cells'\": \"{1: {'metadata': {'execution': {'iopub.execute_input': '2026-05-02T10:47:19.790405Z', \"", " \"'iopub.status.busy': '2026-05-02T10:47:19.789324Z', 'iopub.status.idle': \"", " \"'2026-05-02T10:47:20.182832Z', 'shell.execute_reply': \"", " \"'2026-05-02T10:47:20.181959Z'}}}, 3: {'metadata': {'execution': \"", " \"{'iopub.execute_input': '2026-05-02T10:47:20.186367Z', 'iopub.status.busy': \"", " \"'2026-05-02T10:47:20.186062Z', 'iopub.status.idle': '2026-05-02T10:47:2 [\u2026]"], "unified_diff": "@@ -39,18 +39,18 @@\n ]\n },\n {\n \"cell_type\": \"code\",\n \"execution_count\": 1,\n \"metadata\": {\n \"execution\": {\n- \"iopub.execute_input\": \"2025-03-30T03:09:13.873605Z\",\n- \"iopub.status.busy\": \"2025-03-30T03:09:13.873129Z\",\n- \"iopub.status.idle\": \"2025-03-30T03:09:14.282146Z\",\n- \"shell.execute_reply\": \"2025-03-30T03:09:14.281127Z\"\n+ \"iopub.execute_input\": \"2026-05-02T10:47:19.790405Z\",\n+ \"iopub.status.busy\": \"2026-05-02T10:47:19.789324Z\",\n+ \"iopub.status.idle\": \"2026-05-02T10:47:20.182832Z\",\n+ \"shell.execute_reply\": \"2026-05-02T10:47:20.181959Z\"\n },\n \"nbsphinx\": \"hidden\"\n },\n \"outputs\": [],\n \"source\": [\n \"import matplotlib.pyplot\\n\",\n \"# We have this here to trigger matplotlib's font cache stuff.\\n\",\n@@ -77,36 +77,36 @@\n ]\n },\n {\n \"cell_type\": \"code\",\n \"execution_count\": 2,\n \"metadata\": {\n \"execution\": {\n- \"iopub.execute_input\": \"2025-03-30T03:09:14.286792Z\",\n- \"iopub.status.busy\": \"2025-03-30T03:09:14.286462Z\",\n- \"iopub.status.idle\": \"2025-03-30T03:09:14.585742Z\",\n- \"shell.execute_reply\": \"2025-03-30T03:09:14.584821Z\"\n+ \"iopub.execute_input\": \"2026-05-02T10:47:20.186367Z\",\n+ \"iopub.status.busy\": \"2026-05-02T10:47:20.186062Z\",\n+ \"iopub.status.idle\": \"2026-05-02T10:47:20.536188Z\",\n+ \"shell.execute_reply\": \"2026-05-02T10:47:20.535267Z\"\n }\n },\n \"outputs\": [],\n \"source\": [\n \"import pandas as pd\\n\",\n \"import numpy as np\\n\",\n \"import matplotlib as mpl\\n\"\n ]\n },\n {\n \"cell_type\": \"code\",\n \"execution_count\": 3,\n \"metadata\": {\n \"execution\": {\n- \"iopub.execute_input\": \"2025-03-30T03:09:14.589457Z\",\n- \"iopub.status.busy\": \"2025-03-30T03:09:14.589081Z\",\n- \"iopub.status.idle\": \"2025-03-30T03:09:14.639517Z\",\n- \"shell.execute_reply\": \"2025-03-30T03:09:14.638527Z\"\n+ \"iopub.execute_input\": \"2026-05-02T10:47:20.539667Z\",\n+ \"iopub.status.busy\": \"2026-05-02T10:47:20.539338Z\",\n+ \"iopub.status.idle\": \"2026-05-02T10:47:20.587331Z\",\n+ \"shell.execute_reply\": \"2026-05-02T10:47:20.586309Z\"\n },\n \"nbsphinx\": \"hidden\"\n },\n \"outputs\": [],\n \"source\": [\n \"# For reproducibility - this doesn't respect uuid_len or positionally-passed uuid but the places here that use that coincidentally bypass this anyway\\n\",\n \"from pandas.io.formats.style import Styler\\n\",\n@@ -123,18 +123,18 @@\n ]\n },\n {\n \"cell_type\": \"code\",\n \"execution_count\": 4,\n \"metadata\": {\n \"execution\": {\n- \"iopub.execute_input\": \"2025-03-30T03:09:14.643038Z\",\n- \"iopub.status.busy\": \"2025-03-30T03:09:14.642710Z\",\n- \"iopub.status.idle\": \"2025-03-30T03:09:14.652299Z\",\n- \"shell.execute_reply\": \"2025-03-30T03:09:14.651583Z\"\n+ \"iopub.execute_input\": \"2026-05-02T10:47:20.590639Z\",\n+ \"iopub.status.busy\": \"2026-05-02T10:47:20.590316Z\",\n+ \"iopub.status.idle\": \"2026-05-02T10:47:20.600127Z\",\n+ \"shell.execute_reply\": \"2026-05-02T10:47:20.599165Z\"\n }\n },\n \"outputs\": [\n {\n \"data\": {\n \"text/html\": [\n \"