excel-list-transform 0.8.4__tar.gz → 0.9__tar.gz

{excel_list_transform-0.8.4/excel_list_transform.egg-info → excel_list_transform-0.9}/PKG-INFO

@@ -1,29 +1,25 @@
 Metadata-Version: 2.4
 Name: excel-list-transform
-Version: 0.8.4
-Summary: Transform a list in excel or CSV
+Version: 0.9
+Summary: Transform table data with configurable row and column changes.
 Author: Tom Björkholm
 Author-email: Tom Björkholm <klausuler_linnet0q@icloud.com>
+License-Expression: MIT
 Project-URL: Source code, https://bitbucket.org/tom-bjorkholm/excel-list-transform
 Classifier: Programming Language :: Python :: 3
-Classifier: License :: OSI Approved :: MIT License
 Classifier: Operating System :: OS Independent
-Requires-Python: <3.13,>=3.12
+Requires-Python: >=3.13
 Description-Content-Type: text/markdown
 License-File: LICENSE.txt
-Requires-Dist: openpyxl>=3.1.5
-Requires-Dist: types-openpyxl>=3.1.5.20250919
-Requires-Dist: pylightxl>=1.61
-Requires-Dist: XlsxWriter>=3.2.9
+Requires-Dist: tableio-cfg-json>=0.3
+Requires-Dist: tableio>=0.9
+Requires-Dist: config-as-json>=1.1
+Requires-Dist: versionreporter>=0.2
 Requires-Dist: argcomplete>=3.6.3
-Requires-Dist: pypi-simple>=1.8.0
-Requires-Dist: requests>=2.32.5
-Requires-Dist: types-requests>=2.32.4.20250913
-Requires-Dist: packaging>=25.0
-Requires-Dist: pip>=25.3
-Requires-Dist: setuptools>=80.9.0
-Requires-Dist: build>=1.3.0
-Requires-Dist: wheel>=0.45.1
+Requires-Dist: pip>=26.1
+Requires-Dist: setuptools>=82.0.1
+Requires-Dist: build>=1.5.0
+Requires-Dist: wheel>=0.47.0
 Dynamic: author
 Dynamic: license-file
 Dynamic: requires-dist
@@ -33,30 +29,47 @@ Dynamic: requires-python
 
 ## Background
 
-This python application was born out of an experience at sail racing events. At the start of the events we received an excel list with participants (from a registration web) to enter into the scoring software and into tool for online notice board. The information was present in the excel file, but the columns were all wrong. To avoid the stressful manual rework of the information in the excel list this application was created.
+This python application was born out of an experience at sail racing events.
+At the start of the events we received an excel list with participants (from
+a registration web) to enter into the scoring software and into tool for
+online notice board. The information was present in the excel file, but the
+columns were all wrong. To avoid the stressful manual rework of the
+information in the excel list this application was created.
 
 ## What it does
 
 This small python application:
 
-* reads data (that is a list with columns) from an excel file or from a comma separate values (CSV) file.
-* split rows in the list (creating separate rows when a cell contains something that can be split to several values, see below)
-* merge rows (if specified columns have the same value in several rows the rows are merged to one row)
-* splits columns in the list (like creating "first name" and "last name" columns from "name" column)
-* merges columns in the list (like creating "name" column from "first name" and "last name" columns)
-* removes columns in the list
-* reorders columns in the list
-* renames columns in the list
-* inserts columns in the list
-* rewrites columns in the list (like transforming telephone numbers from local/national format to international format)
-* writes the resulting data (that is a list with columns) to an excel file or to a comma separate values (CSV) file.
-
-How this is done is governed by a configuration file. The application can create a number of example configuration files with accompanying description text files.
+- reads data (that is a list with columns) from an excel file, an ODS file,
+  or from a comma separated values (CSV) file.
+- split rows in the list (creating separate rows when a cell contains
+  something that can be split to several values, see below)
+- merge rows (if specified columns have the same value in several rows
+  the rows are merged to one row)
+- splits columns in the list (like creating "first name" and "last name"
+  columns from "name" column)
+- merges columns in the list (like creating "name" column from "first name"
+  and "last name" columns)
+- removes columns in the list
+- reorders columns in the list
+- renames columns in the list
+- inserts columns in the list
+- rewrites columns in the list (like transforming telephone numbers from
+  local/national format to international format)
+- writes the resulting data (that is a list with columns) to an excel file,
+  an ODS spreadsheet file, a comma separated values (CSV) file, or
+  any of a number of other file formats.
+
+How this is done is governed by a configuration file. The application can
+create a number of example configuration files with accompanying description
+text files.
 
 ## Installing it
 
-If you want to use it, install it using pip. A precondition is that you have Python installed on you computer. See version table below for information on needed Python version.
-Python can be downloaded from [https://www.python.org/downloads/](https://www.python.org/downloads/).
+If you want to use it, install it using pip. A precondition is that you have
+Python installed on your computer. See version table below for information
+on needed Python version. Python can be downloaded
+from [https://www.python.org/downloads/](https://www.python.org/downloads/).
 
 ### Installing on mac and Linux
 
@@ -94,6 +107,7 @@ pip install --upgrade excel-list-transform
 | 0.8.3   | 23 Jul 2025 | 3.13 or newer   | Add split-row and merge-row         |
 | 0.8.4   | 23 Nov 2025 | 3.12.x          | Backport 0.8.5 to Python 3.12       |
 | 0.8.5   | 23 Nov 2025 | 3.13 or newer   | Adapted to Python 3.14              |
+| 0.9     | 06 Jun 2026 | 3.13 or newer   | Many new input/output formats       |
 
 ## Running the application
 
@@ -125,43 +139,62 @@ python -m excel_list_transform migrate-cfg -i old.cfg -o new.cfg
 
 ## Suggested way to get started
 
- 1. Use the "cfg-example" sub-command to generate a few example configuration (.cfg) files with description (.txt) files.
- 2. Read the example configuration (.cfg) files and the accompanying description (.txt) files.
+ 1. Use the "cfg-example" sub-command to generate a few example configuration
+    (.cfg) files with description (.txt) files.
+ 2. Read the example configuration (.cfg) files and the accompanying
+    description (.txt) files.
  3. Find an example that is close to what you want to achieve.
  4. Modify that configuration file to achieve what you want to achieve.
- 5. Use the "transform" sub-command to read your data and output it transformed or reorganized according to your modified configuration file.
- 6. Read the produced output. If necessary go back to step 4 and adjust how the data is transformed.
+ 5. Use the "transform" sub-command to read your data and output it transformed
+    or reorganized according to your modified configuration file.
+ 6. Read the produced output. If necessary go back to step 4 and adjust how the
+    data is transformed.
 
 ### Example configuration files
 
-When using the "cfg-example" sub-command to generate an example configuration file (say example.cfg) a text file describing the configuration and the syntax of the configuration file is also generated. If the example configuration file is named example.cfg, then the text file descriging the configuration is named example.txt.
+When using the "cfg-example" sub-command to generate an example configuration
+file (say example.cfg) a text file describing the configuration and the syntax
+of the configuration file is also generated. If the example configuration
+file is named example.cfg, then the text file describing the configuration
+is named example.txt.
 
-You can generate several example configuration files each with an accompanying text file descriping it.
+You can generate several example configuration files each with an accompanying
+text file describing it.
 
-Read the text file describing the configuration file while looking at the configuration file to understand the syntax and the possible options.
+Read the text file describing the configuration file while looking at the
+configuration file to understand the syntax and the possible options.
 
 ## Performance
 
-This application is written for the moderate amounts of data when registering participants for the majority of sports events. If you have millions of rows this application is not for you.
+This application is written for the moderate amounts of data when
+registering participants for the majority of sports events. If you have
+millions of rows this application is not for you.
+
+With an input file consisting of 20 columns producing an output file of
+11 columns I have measured the following performance:
 
-With an input file consisting of 20 columns producing an output file of 11 columns I have measured the following performance on a MacBook Air (laptop) from 2020:
+| number of rows |   on MacBook Air M4   | on MacMini M4 Pro     |
+|----------------|-----------------------|-----------------------|
+|            100 | less than 0.2 seconds | less than 0.2 seconds |
+|            500 |                       | less than 2 seconds   |
 
-* 1 000 rows processed in less than 0.5 seconds
-* 10 000 rows processed in less than 4 seconds
-* 80 000 rows processed in less than 30 seconds
-* 120 000 rows processed in 40 seconds
+(A performance related fix in a library this application depends on is
+ expected soon.)
 
-Naturally your performance will be different based on computer hardware, operating system and Python version. Generally it should be reasonably fast for less than 10 000 rows, painfully slow but somewhat usable up to 100 000 rows and probably so slow that it is unusable for more than 100 000 rows.
+Naturally your performance will be different based on computer
+hardware, operating system and Python version.
 
 ## Description of how to write/change the configuration file
 
-The configuration file is in JSON syntax. [https://en.wikipedia.org/wiki/JSON](https://en.wikipedia.org/wiki/JSON)
+The configuration file is in JSON syntax.
+[https://en.wikipedia.org/wiki/JSON](https://en.wikipedia.org/wiki/JSON)
 
 The keywords and the nesting is important. The order of keywords
 have no significance (the examples use alphabetical order).
 Indentation and line breaks have no significance.
 
-The encoding for the configuration file must be UTF-8. (US-ACII is a subset of UTF-8.)
+The encoding for the configuration file must be UTF-8. (US-ASCII is a
+subset of UTF-8.)
 
 It is recommended that you let the command generate a configuration
 file and then edit that file to match your needs. It is NOT recommended
@@ -172,14 +205,15 @@ that the user writes the configuration file from scratch.
 The keyword **column_ref** is used to tell if the configuration
 references columns by name (value *"BY_NAME"*) or by number
 (value *"BY_NUMBER"*). The syntax of parts of the configuration file
-is slightly different depending on the how columns are referenced.
+is slightly different depending on how columns are referenced.
 Thus, you first have to decide how you want to reference columns.
 
 Generally it is easier to write a correct configuration using *"BY_NAME"*,
-so *"BY_NAME"* is recommended when possible. *"BY_NAME"* imposes a few restrictions:
+so *"BY_NAME"* is recommended when possible. *"BY_NAME"* imposes a few
+restrictions:
 
-* each column need to have a unique text at the first line to use as column name.
-* the column names need to be stable and known.
+- each column needs to have a unique text at the first line to use as column name.
+- the column names need to be stable and known.
 
 If you cannot meet these restrictions you will have to reference the
 columns by number *"BY_NUMBER"*. When referencing the columns by number
@@ -191,49 +225,37 @@ right. The leftmost column is number 0.
 
 ## Type of input and output file
 
-The type of input file to read is determined by **"in_type"**.
-The type of output file to write is determined by **"out_type"**.
-**"in_type"** and **"out_type"** can have values *"CSV"* or *"EXCEL"*.
-
-Excel files can be read and written using three libraries.
-**"in_excel_library"** and **"out_excel_library"** can have values
-*"OPENPYXL"*, *"XLSXWRITER"* or *"PYLIGHTXL"*. These are different
-third party libraries that can read/write excel. My experience
-is that *"PYLIGHTXL"* most often is able to read and write excel
-files correctly. If you have trouble reading/writing your
-particular excel file, please try different combinations of
-these libraries. **"in_excel_library"** is always needed in
-the configuration file but is not used if the input is CSV.
-**"out_excel_library"** is always needed in the configuration file
-but is not used if the output is CSV.
-
-Currently *"PYLIGHTXL"* appears to be best to write files for
-Microsoft Excel to open without complaints. But *"OPENPYXL"*
-appears to be best to write files to be imported by
-[https://www.racingrulesofsailing.org](https://www.racingrulesofsailing.org).
-When newer versions arrive this might change...
-
-Comma separated values files (CSV files) may differ slightly
-depening on the programs used to read/write them and the locale
-used. **"in_csv_dialect"** and **"out_csv_dialect"** changes how CSV files
-are read and written. They are always needed in the configuration
-file, but are not used if the input and output are excel files.
-
-Comma separated values files might have different encoding for
-the text in the file. [https://en.wikipedia.org/wiki/Character_encoding](https://en.wikipedia.org/wiki/Character_encoding)
-This is specified with **"in_csv_encoding"** and **"out_csv_encoding"**.
-Unless you know that you need another encoding leave these as
-in the generated example configuration. (In version 0.5 these
-configuration parameters are missing. To be compatible with 0.5
-configuration files "in_csv_encoding" defaults to "utf_8_sig"
-and "out_csv_encoding" defaults to "utf-8" if missing in the
-configuration file.)
+The type of input file to read is configured in the **"input_table"**
+section. The type of output file to write is configured in the
+**"output_table"** section. These sections use the TableIO JSON
+configuration syntax.
+
+The most important keyword in each table section is **"format_name"**.
+Generated examples commonly use *"Excel"* or *"CSV"*, but TableIO may
+support more formats. In most cases you should leave **"implementation"**
+missing or set to *null*. Then TableIO chooses a suitable implementation.
+If you know that you need a specific implementation, you can add it
+manually.
+
+CSV files may differ slightly depending on the programs used to read/write
+them and the locale used. CSV-specific settings are configured in the
+nested **"csv"** section inside **"input_table"** or **"output_table"**.
+The **"character_encoding"** keyword in the table section controls the
+text encoding.
+[https://en.wikipedia.org/wiki/Character_encoding](https://en.wikipedia.org/wiki/Character_encoding)
+
+Output tables can request extra presentation features. Set
+**"output_borders"** to *true* to request table borders. Set
+**"output_filtered_table"** to *true* to request a filtered table area.
+These features are ignorable requests. TableIO will prefer an
+implementation that can provide them, but the transform can still write
+the output if the selected file format cannot represent them.
 
 ## Extra spaces in excel input files
 
 When viewing an excel file in excel it is very hard to notice if
-some string value in a cell has trailing white space. These trailing
-trailing spaces can make the further processing of a file difficult
+some string value in a cell has trailing whitespace. These trailing
+spaces can make the further processing of a file difficult
 as the strings in the file are not what you thought they are.
 (This especially is a problem if you have trailing spaces in a
 cell on the first line, and refer to columns by their names.)
@@ -243,7 +265,7 @@ to strip off leading and trailing whitespace from all columns
 values read from the first line of the excel input file.
 The configuration **"in_excel_values_strip"** can be set to true,
 to strip off leading and trailing whitespace from all columns
-values read from from the other lines (not the first line) of
+values read from the other lines (not the first line) of
 the excel input file. (In version 0.6.2 and earlier these are
 missing. To be compatible with version 0.6.2 and earlier
 **"in_excel_col_name_strip"** and  **"in_excel_values_strip"**
@@ -251,10 +273,10 @@ defaults to false if missing in the configuration file.)
 
 ## Column manipulation
 
-A number or records starting with "s" and a number describe
+A number of records starting with "s" and a number describe
 column manipulation to be done. These manipulations are done
-in order of the number: s1_(something) before s2_(something),
-before s3_(something). As the "s" number records might add, remove
+in order of the number: s01_(something) before s02_(something),
+before s03_(something). As the "s" number records might add, remove
 or rename columns, it is important to keep track of the order that
 they are applied.
 
@@ -266,12 +288,12 @@ referenced by number.
 
 The first operation is to split rows based on column values.
 This operation is configured using the **"s01_split_rows"** record,
-that have an array of splits to be done. Each row split has the
+that has an array of splits to be done. Each row split has the
 following keys: **"column"**, **"separators"** and **"not_separators"**.
 
 The **"column"** keyword is used to identify the column that is
 split into several rows. This is a column number in the case of
-*"BY_NUMBER"*, and a column name/title in the sace of *"BY_NAME"*.
+*"BY_NUMBER"*, and a column name/title in the case of *"BY_NAME"*.
 
 New rows will be created so that the parts of the identified
 column will be put in that column only one part per row.
@@ -283,7 +305,7 @@ these strings are present in the identified column it is seen
 as the separator between the parts of the column value that go
 into different rows.
 
-**"not_separators"** take as arguement a list of strings. These strings
+**"not_separators"** take as argument a list of strings. These strings
 are not regarded as separators even if they include the strings
 of one or more separator. (For instance ";" could be a separator,
 but using **"not_separators"** the string "\\;" could be seen as not
@@ -293,14 +315,14 @@ a separator.)
 
 The next operation is to merge rows based on column values.
 This is the opposite operation to the splitting of rows.
-Row mergins is configured using the **"s02_merge_rows"** record,
-that have an array of merges to be done. Each row merge have
+Row merging is configured using the **"s02_merge_rows"** record,
+that has an array of merges to be done. Each row merge has
 the following keys: **"columns"** and **"separator"**.
 
 The **"columns"** keyword is used to identify the columns that need
 to have identical values to merge two or more rows. The **"columns"**
-keyword take a list of columns. These are column numbers in the case of
-*"BY_NUMBER"*, and a column names/titles in the sace of *"BY_NAME"*.
+keyword takes a list of columns. These are column numbers in the case of
+*"BY_NUMBER"*, and column names/titles in the case of *"BY_NAME"*.
 
 For each column that has the same value for all rows merged, that
 value will be in the merged row. When rows being merged have different
@@ -320,7 +342,7 @@ for customers in the following format:
 | Brewery     | Beer   | Smith + Bush  |
 | Dairy       | Milk   | Jones         |
 
-But for distrubuting it to customers you would like to have the
+But for distributing it to customers you would like to have the
 list in the following format:
 
 | To        | What          | From               |
@@ -330,27 +352,27 @@ list in the following format:
 | Bush      | Beer          | Brewery            |
 
 To do this transformation we use the **"s01_split_rows"** to split
-rows base on the "To" column using " + " as separator.
+rows based on the "To" column using " + " as separator.
 Then we use **"s02_merge_rows"** to merge the rows that have
 identical values in the "To" column.
 
 ### "s03_split_columns"
 
-The first operation that is done is splitting of columns.
-The key **"s03_split_columns"** have an array of splits to be
+The first column operation that is done is splitting of columns.
+The key **"s03_split_columns"** has an array of splits to be
 done. (When the list of splits has more than one split,
 the least confusion is to split columns to the right before
 columns to the left. Named references also helps to avoid
 confusion.)
 
 Each split has the following keys: **"column"**, **"separator"** and
-**"where"**. In the case of number column references the there is
+**"where"**. In the case of number column references there is
 also the key **"store_single"**. In the case of named column references
 there is instead the key **"right_name"**.
 
-**"column"** take as argument the column to be split. This is a
+**"column"** takes as argument the column to be split. This is a
 column number in the case of *"BY_NUMBER"*, and a column name/title
-in the sace of *"BY_NAME"*.
+in the case of *"BY_NAME"*.
 
 **"separator"** is a string of characters that indicate the position
 where the column shall be split. (For instance a single space
@@ -359,7 +381,7 @@ if splitting between two words.)
 **"where"** can either have the value *"RIGHTMOST"* or the value
 *"LEFTMOST"*. This is used if the separator string is present
 more than once in the column value to split. The split is then
-done at the leftmost or rightmost occurence according to the
+done at the leftmost or rightmost occurrence according to the
 value of **"where"**.
 
 **"right_name"** is only used if column references are *"BY_NAME"*.
@@ -379,11 +401,11 @@ always stored in the column with the original name.
 
 **"s04_remove_columns"** is only used with column references *"BY_NUMBER"*.
 The value of **"s04_remove_columns"** is a list of column numbers to
-remove. (For columns references *"BY_NAME"* see **"s10_column_order"**.)
+remove. (For column references *"BY_NAME"* see **"s10_column_order"**.)
 
 ### "s05_merge_columns"
 
-The key **"s05_merge_columns"** have an array of merges to be done.
+The key **"s05_merge_columns"** has an array of merges to be done.
 Each merge have the keys **"columns"** and **"separator"**.
 
 **"columns"** have a list of column references. If *"BY_NAME"* the
@@ -399,16 +421,16 @@ the column values being merged.
 The key **"s06_place_columns_first"** has a value that is a list of the
 column numbers to be placed first in order. This step re-orders the
 columns.
-(For columns references *"BY_NAME"* see **"s10_column_order"**.)
+(For column references *"BY_NAME"* see **"s10_column_order"**.)
 
 ### "s07_rename_columns"
 
 The key **"s07_rename_columns"** has a value that is a list of column rename
 operations. Each column rename operation has the keys **"column"** and **"name"**.
 
-**"column"** is the number/name of the column before renameing. This is a
+**"column"** is the number/name of the column before renaming. This is a
 column number in the case of *"BY_NUMBER"*, and a column name/title
-in the sace of *"BY_NAME"*.
+in the case of *"BY_NAME"*.
 
 **"name"** is the new name/title of the column identified by **"column"**.
 
@@ -443,7 +465,7 @@ keys. **"kind"** can have the values: *"STRIP"*, *"REMOVECHARS"*,
 **"kind"** value *"STRIP"* shall have the keys: **"kind"**, **"case"**, **"chars"**
 and **"column"**. This case means that the characters in **"chars"** shall
 be stripped off the beginning and end of the column value. If key
-**"chars"** is empty string, then white space is stripped off.
+**"chars"** is empty string, then whitespace is stripped off.
 
 **"kind"** value *"REMOVECHARS"* shall have the keys: **"kind"**, **"case"**,
 **"chars"** and **"column"**. This case means that the characters in **"chars"**
@@ -461,7 +483,7 @@ and if a sub-string of the column value equals this string that part is
 replaced with the value of key **"to"**.
 
 **"column"** identifies the column to rewrite. This is a column number in the
-case of *"BY_NUMBER"*, and a column name/title in the sace of *"BY_NAME"*.
+case of *"BY_NUMBER"*, and a column name/title in the case of *"BY_NAME"*.
 
 **"chars"** is a list of characters written as a string. These characters
 are removed or stripped off the beginning/end depending on the **"kind"**
@@ -471,8 +493,8 @@ value.
 value of **"from"** shall be case sensitive or not. Possible values are
 *"MATCH_CASE"* and *"IGNORE_CASE"*.
 
-**"from"** specifies what the part of the column value shall be to substituted
-when matching. The from part in the substitute from something to something.
+**"from"** specifies what part of the column value shall be substituted
+when matching.
 
 **"to"** specifies the string that substitution will replace **"from"** with.
 
@@ -485,22 +507,21 @@ Columns not mentioned in **"s10_column_order"** will not be output,
 and will thus be removed.
 (For *"BY_NUMBER"* see **"s04_remove_columns"** and **"s06_place_columns_first"**.)
 
-## Backward compatibility of configuration keywords
+## Utility for recoding text files
 
-Old keywords according to the table below are automatically renamed to the new keywords, when reading the configuration file.
+When working with text based files like comma separated values (CSV)
+the file may have an incorrect character encoding, and even worse
+you may not know what character encoding was used to create the file.
+As a small tool for these situations the excel-list-transform includes
+a small recode utility. Using this you can by trial and error recode
+from different encodings until you find which encoding works. (This
+may be the way to figure out which character encoding to write into
+a configuration file.)
 
-| Version 0.7.13 and lower | Version 0.8 and higher  |
-|--------------------------|-------------------------|
-|  -                       | s01_split_rows          |
-|  -                       | s02_merge_rows          |
-| s1_split_columns         | s03_split_columns       |
-| s2_remove_columns        | s04_remove_columns      |
-| s3_merge_columns         | s05_merge_columns       |
-| s4_place_columns_first   | s06_place_columns_first |
-| s5_rename_columns        | s07_rename_columns      |
-| s6_insert_columns        | s08_insert_columns      |
-| s7_rewrite_columns       | s09_rewrite_columns     |
-| s8_column_order          | s10_column_order        |
+```python
+python3 -m excel_list_transform.recode --help
+python3 -m excel_list_transform.recode -i a.txt -o b.txt --from cp1250 --to utf-8
+```
 
 ## Source code
 
@@ -508,7 +529,9 @@ Source code and tests are available at [https://bitbucket.org/tom-bjorkholm/exce
 
 ## Test summary
 
-* Test result: 4119 passed in 14s
-* No Flake8 warnings.
-* No mypy errors found.
-* 0.8.4 built and tested using python version: Python 3.12.6
+- Test result: 1368 passed in 64s (0:01:04)
+- No flake8 warnings.
+- No mypy errors found.
+- No python layout warnings.
+- Built version(s): 0.9
+- Build and test using Python 3.14.5

excel_list_transform-0.9/README.md

@@ -0,0 +1,116 @@
+# excel-list-transform
+
+## Background
+
+This python application was born out of an experience at sail racing events. At the start of the events we received an excel list with participants (from a registration web) to enter into the scoring software and into tool for online notice board. The information was present in the excel file, but the columns were all wrong. To avoid the stressful manual rework of the information in the excel list this application was created.
+
+## Using it
+
+If you want to use it install it using pip from [https://pypi.org/project/excel-list-transform](https://pypi.org/project/excel-list-transform).
+There is no need to download anything from Bitbucket to use the application.
+
+### Installing on mac and Linux
+
+````sh
+pip3 install --upgrade excel-list-transform
+````
+
+### Installing on Microsoft Windows
+
+````sh
+pip install --upgrade excel-list-transform
+````
+
+### Information for use
+
+Please see [https://pypi.org/project/excel-list-transform](https://pypi.org/project/excel-list-transform) or please see README_pypi.md
+
+## What it does
+
+This small python application:
+
+- reads data (that is a list with columns) from an excel file, an ODS file,
+  or from a comma separated values (CSV) file.
+- splits columns in the list (like creating "first name" and "last name"
+  columns from "name" column)
+- merges columns in the list (like creating "name" column from "first name"
+  and "last name" columns)
+- removes columns in the list
+- reorders columns in the list
+- renames columns in the list
+- inserts columns in the list
+- rewrites columns in the list (like transforming telephone numbers from
+  local/national format to international format)
+- writes the resulting data (that is a list with columns) to an excel file,
+  an ODS spreadsheet file, a comma separated values (CSV) file, or
+  any of a number of other file formats.
+
+How this is done is governed by a configuration file. The application can create a number of example configuration files with accompanying description text files.
+
+## Cloning
+
+This repository uses submodules. Clone it with:
+
+```sh
+git clone --recurse-submodules \
+  git@bitbucket.org:tom-bjorkholm/excel-list-transform.git
+```
+
+If you already cloned without submodules, initialize them with:
+
+```sh
+git submodule update --init --recursive
+```
+
+To update the checked-out submodule revisions:
+
+```sh
+git submodule update --remote --merge
+```
+
+## Supported Python versions
+
+- Package runtime baseline: Python 3.13 or newer
+- Maintainer validation target: Python 3.13, and 3.14
+- Main day-to-day development: usually the newest supported Python version
+
+## Development workflow
+
+On macOS and Linux, the normal workflow is:
+
+1. Run `./run_setup_build_environment.py` once after cloning or when the
+   build environment needs to be recreated.
+2. Run `./run_build.py` for the normal build-and-test cycle.
+3. Run `./run_clean_build.py` before review or release work that needs a
+   completely fresh build.
+
+The helper scripts are:
+
+- `run_setup_build_environment.py`
+  Create or refresh the build environment.
+- `run_build.py`
+  Build the package and run the configured checks in the project virtual
+  environment.
+- `run_clean.py`
+  Remove files generated by the build system.
+- `run_clean_build.py`
+  Perform a clean build from scratch. This is especially useful because some
+  duplicate-code diagnostics only appear on a clean build.
+- `run_pypi_build.py`
+  Create the distribution artifacts intended for PyPI publishing.
+
+The standard verification suite includes pytest, pylint, flake8, and mypy.
+After a build, the generated reports can be browsed through
+`reports/index.html`.
+
+After running `run_build.py` or `run_clean_build.py`, you can manually test
+the built and installed application in the virtual environment `./venv`.
+
+## Test summary
+
+- Test result: 1368 passed in 64s (0:01:04)
+- No flake8 warnings.
+- No mypy errors found.
+- No python layout warnings.
+- Built version(s): 0.9
+- Build and test using Python 3.14.5