Addition of skew, add_prefix, add_suffix, count, std functions

[nipsn]

Feature

• Please insert link to associated issue here: /issues/14

What does this change introduce?

An implementation of the skew function: https://pandas.pydata.org/docs/reference/api/pandas.DataFrame.skew.html#pandas.DataFrame.skew

An implementation of the add_prefix and add_suffix function: https://pandas.pydata.org/docs/reference/api/pandas.DataFrame.add_prefix.html https://pandas.pydata.org/docs/reference/api/pandas.DataFrame.add_suffix.html

Observations:

• In Pandas the index attribute does not change the result (only the columns are changed, not the indexes). In this implementation, prefixes or suffixes can be added to indexes in addition to columns.

An implementation of the count function:

Observations:

• In accordance with the correspondence between q nulls and Python nulls established in the .pd conversion, the empty string is regarded as a null value for columns of type symbol.

An implementation of the std function:

https://pandas.pydata.org/docs/reference/api/pandas.DataFrame.std.html#pandas.DataFrame.std

General

• [ ] Has an example been added to demo the new feature?
• [ ] Have existing examples been updated or tested?
• [ ] Have you added any new Environment Variables/Configuration Options? If yes please tick the boxes below as applicable
  • [ ] Addition to reimporter logic within src/pykx/pykx.q and src/pykx/reimporter.py
  • [ ] Have updated the src/pykx/util.py logic which is used for environment variable
• [ ] If there have been any dependency updates have they been reflected in all files?
  • [ ] pyproject.toml
  • [ ] docs/getting-started/installing.md
  • [ ] conda-recipe/meta.yaml
  • [ ] README.md
• [ ] If any examples have been updated has it's associated .zip been updated

Code

• [x] Has all temporary code used during development been removed?
• [x] Has all commented out (unused) code been removed?
• [x] Where reasonable have you ensured there is no duplication of existing code?
• [x] If applicable for your use-case have you ensured that the code is performant?

Testing

• [x] Have unit tests been created or existing ones updated to test this new functionality?

Documentation

• [x] Has documentation been added for all public code?
• [ ] Has a release note been included for the new feature?
• [ ] Has any documentation which would benefit from this feature been updated to use the most up to date functionality?
• [ ] If a new class has been added has a documentation stub .md file associated with it been created?
• [ ] If any documentation page has been created has it been added to mkdocs.yml
• [x] Have you checked your changes with a spell checker? (US English)

[nipsn]

@cmccarthy1 @rianoc-kx Please review our contributions and feel free to give any kind of feedback. Thanks in advance.

[cmccarthy1]

Thanks for the changes @marcosvm13, I've approved but @rianoc-kx will need to approve this week additionally to get this included in the next release, we'll look to get this done this week for release with our 2.3 release coming up next week

[rianoc-kx]

I had made my suggested fixes and created a pull request to your repo to review

https://github.com/hablapps/pykx/pull/31

We will be doing a larger refactor of PyKX in a similar fashion to use cleaner q code instead of building F-strings which make the code hard to read and refactor.