CVS log for pkgsrc/math/py-simpleeval/distinfo

Up to [cvs.NetBSD.org] / pkgsrc / math / py-simpleeval

Request diff between arbitrary revisions

Keyword substitution: kv
Default branch: MAIN

py-simpleeval: updated to 1.0.3

1.0.3

Spelling fixes in documentation, docstrings & tests (thanks @kurtmckee !)
Fix support for 3.14 (deprecated features actually being removed, so getattr use was incorrect).

py-simpleeval: updated to 1.0.2

1.0.2
No functional changes - but release with the pip version removed from requirements.

1.0.1
Update the packaging / build after the 1.0.0 release.
No new features since 1.0.0

1.0.0
Fix a sandbox escape via generators and _frame methods.
Supporting dictionary comprehensions
A custom exception rather than KeyError when names not found
Dropping support for old python versions - if you need pre 3.9, then you can use an older version
Various cleanups & tidying warnings, deprecation warnings etc.

py-simpleeval: updated to 0.9.13

0.9.13

Better handling of empty strings passed as input.
Fix the shift safe number issue from 0.9.12
More minor pylint / etc fixes / cleanups (general code quality)
separate .parse
Allow setting up completely empty {} operators / functions
Add extra bit-ops
Add @daxamin to contributors ?
Version bump stuff.
other readme tweaks
star expressions, eg x = {"a": 1, "b": 2, **c}

py-simpleeval: updated to 0.9.12

0.9.12
KInd of hoping this is the last 0.9 release, and I find time to stablize as 1.0, and start the 2.0 work some time soon...

Changelog:

Remove Cyclic references (memory leak)
Add left & right shift operations (<< and >>)
Switch to GH actions & CodeCov.io for CI tests
Add extra contributors details
Reformat w/ Black + isort, and have linting of those in CI

py-simpleeval: updated to 0.9.11

0.9.11:
Revert / convert to setup.py-less build system using pypa build

math: Replace RMD160 checksums with BLAKE2s checksums

All checksums have been double-checked against existing RMD160 and
SHA512 hashes

math: Remove SHA1 hashes for distfiles

py-simpleeval: updated to 0.9.10

0.9.10:
Unknown changes

py-simpleeval: updated to 0.9.8

0.9.8:
Unknown changes

py-simpleeval: updated to 0.9.6

0.9.6:
Unknown changes.

py-simpleeval: update to 0.9.5

0.9.5:
Python 3 compatibility.
Bug fixes.

Add SHA512 digests for distfiles for math category

Problems found locating distfiles:
	Package dfftpack: missing distfile dfftpack-20001209.tar.gz
	Package eispack: missing distfile eispack-20001130.tar.gz
	Package fftpack: missing distfile fftpack-20001130.tar.gz
	Package linpack: missing distfile linpack-20010510.tar.gz
	Package minpack: missing distfile minpack-20001130.tar.gz
	Package odepack: missing distfile odepack-20001130.tar.gz
	Package py-networkx: missing distfile networkx-1.10.tar.gz
	Package py-sympy: missing distfile sympy-0.7.6.1.tar.gz
	Package quadpack: missing distfile quadpack-20001130.tar.gz

Otherwise, existing SHA1 digests verified and found to be the same on
the machine holding the existing distfiles (morden).  All existing
SHA1 digests retained for now as an audit trail.

Add py-simpleeval
A quick single-file MIT-Licenced library for easily adding evaluatable
expressions into python projects. Say you want to allow a user to set an alarm
volume, which could depend on the time of day, alarm level, how many previous
alarms had gone off, and if there is music playing at the time.

Or if you want to allow simple formulae in a web application, but don't want
to give full eval() access, or don't want to run in javascript on the client side.

It's deliberately very simple, just a single file you can dump into a project,
or import from pypi (pip or easy_install).

Internally, it's using the amazing python ast module to parse the expression,
which allows very fine control of what is and isn't allowed. It should be
completely safe in terms of what operations can be performed by the expression.

The only issue I know to be aware of is that you can create an expression which
takes a long time to evaluate, or which evaluating requires an awful lot of
memory, which leaves the potential for DOS attacks. There is basic protection
against this, and you can lock it down further if you desire.

You should be aware of this when deploying in a public setting.

The defaults are pretty locked down and basic, and it's very easy to add whatever
extra specific functionality you need (your own functions, variable/name lookup, etc).