xlcalculator 0.2.7

Run tests

Setup your environment:

virtualenv -p 3.7 ve
ve/bin/pip install -e .[test]

From the root xlcalculator directory:

ve/bin/py.test -rw -s --tb=native

Or simply use tox:

tox

Run Example

From the examples/common_use_case directory:

python use_case_01.py

Adding/Registering Excel Functions

Excel function support can be easily added.

Fundamental function support is found in the xlfunctions directory. The functions are thematically organised in modules.

Excel functions can be added by any code using the xlfunctions.xl.register() decorator. Here is a simple example:

from xlcalculator.xlfunctions import xl

@xl.register()
@xl.validate_args
def ADDONE(num: xl.Number):
    return num + 1

The @xl.validate_args decorator will ensure that the annotated arguments are converted and validated. For example, even if you pass in a string, it is converted to a number (in typical Excel fashion):

>>> ADDONE(1):
2
>>> ADDONE('1'):
2

If you would like to contribute functions, please create a pull request. All new functions should be accompanied by sufficient tests to cover the functionality. Tests need to be written for both the Python implementation of the function (tests/xlfunctions) and a comparison with Excel (tests/xlfunctions_vs_excel).

Excel number precision

Excel number precision is a complex discussion.

It has been discussed in a Wikipedia page.

The fundamentals come down to floating point numbers and a contention between how they are represented in memory Vs how they are stored on disk Vs how they are presented on screen. A Microsoft article explains the contention.

This project is attempting to take care while reading numbers from the Excel file to try and remove a variety of representation errors.

Further work will be required to keep numbers in-line with Excel throughout different transformations.

From what I can determine this requires a low-level implementation of a numeric datatype (C or C++, Cython??) to replicate its behaviour. Python built-in numeric types don’t replicate behaviours appropriately.

Unit testing Excel formulas directly from the workbook.

If you are interested in unit testing formulas in your workbook, you can use FlyingKoala. An example on how can be found here.

TODO

• Do not treat ranges as a granular AST node ut instead as an operation “:” of two cell references to create the range. That will make implementing features like A1:OFFSET(...) easy to implement.

• Support for alternative range evaluation: by ref (pointer), by expr (lazy eval) and current eval mode.

  • Pointers would allow easy implementations of functions like OFFSET().

  • Lazy evals will allow efficient implementation of IF() since execution of true and false expressions can be delayed until it is decided which expression is needed.

• Implement array functions. It is really not that hard once a proper RangeData class has been implemented on which one can easily act with scalar functions.

• Improve testing

• Refactor model and evaluator to use pass-by-object-reference for values of cells which then get “used”/referenced by ranges, defined names and formulas

• Handle multi-file addresses

• Improve integration with pyopenxl for reading and writing files xample of problem space

0.2.7 (2020-09-22)

• Add functions: ISBLANK(), ISNA(), ISTEXT(), NA()

0.2.6 (2020-09-21)

• Add COUNTIIF() and COUNTIFS() function support.

0.2.5 (2020-09-21)

• Add SUMIFS() support.

0.2.4 (2020-09-09)

• Updated README with supported functions.

• Fix bug in ModelCompiler extract method where a defined name cell was being overwritten with the cell from one of the terms contained within the formula. Added a test for this.

• Move version of yearfrac to 0.4.4. That project has removed a dependency on the package six.

0.2.3 (2020-08-18)

• In-boarded xlfunctions.

• Bugfix COUNTA.

  • Now supports 256 arguments.

• Updated README. Includes words on xlfunction.

• Changed licence from GPL-3 style to MIT Style.

0.2.2 (2020-05-28)

• Make dependency resolution part of the execution.

  • AST eval’ing takes care of depedency resolution.

  • Provide cycle detection with reporting.

  • Implemented a specific evaluation context. That makes cache control, namespace customization and data encapsulation much easier.

• Add more tokenizer tests to increase coverage.

0.2.1 (2020-05-28)

• Use a less intrusive way to patch openpyxl. Instead of permanently patching the reader to support cached formula values, mock is used to only patch the reader while reading the workbook.

  This way the patches do not interfere with other packages not expecting these new classes.

0.2.0 (2020-05-28)

• Support for delayed node evaluation by wrapping them into expressions. The function will eval the expression when needed.

• Support for native Excel data types.

• Enable and update Excel file based function tests that are now working properly.

• Flake8 source code.

0.1.0 (2020-05-25)

• Refactored xlcalculator types to be more compact.

• Reimplemented evaluation engine to not generate Python code anymore, but build a proper AST from the AST nodes. Each AST node supports an eval() function that knows how to compute a result.

  This removes a lot of complexities around trying to determine the evaluation context at code creation time and encoding the context as part of the generated code.

• Removal of all special function handling.

• Use of new xlfunctions implementation.

• Use Openpyxl to load the Excel files. This provides shared formula support for free.

0.0.1b (2020-05-03)

• Initial release.