version: 2

updates:

- package-ecosystem: "github-actions"

directory: "/"

schedule:

interval: "weekly"

name: Python package

on: [push, pull_request, workflow_dispatch]

permissions:

contents: read

jobs:

build:

strategy:

matrix:

python-version: ["3.7", "3.8", "3.9", "3.10", "3.11", "3.12", "3.13", "3.13t"]

include:

- experimental: false

- os: ubuntu-latest

- python-version: "3.7"

os: ubuntu-22.04

runs-on: ${{ matrix.os }}

continue-on-error: ${{ matrix.experimental }}

steps:

- uses: actions/checkout@v7

- name: Set up Python ${{ matrix.python-version }}

uses: actions/setup-python@v6

with:

python-version: ${{ matrix.python-version }}

allow-prereleases: ${{ matrix.experimental }}

- name: Install project

run: |

- name: Lint with flake8

run: |

- name: Test

run: |

build/

cover/

dist/

/env/

Copyright (C) 2010, 2011 Sebastian Thiel and contributors

All rights reserved.

Redistribution and use in source and binary forms, with or without

modification, are permitted provided that the following conditions

are met:

* Redistributions of source code must retain the above copyright

notice, this list of conditions and the following disclaimer.

* Redistributions in binary form must reproduce the above copyright

notice, this list of conditions and the following disclaimer in the

documentation and/or other materials provided with the distribution.

* Neither the name of the async project nor the names of

its contributors may be used to endorse or promote products derived

from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS

"AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT

LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR

A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT

OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,

SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED

TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR

PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF

LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING

NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS

SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

# Include the license file

include LICENSE

.PHONY: all clean release force_release

all:

@grep -Ee '^[a-z].*:' Makefile | cut -d: -f1 | grep -vF all

clean:

rm -rf build/ dist/ .eggs/ .tox/

force_release: clean

./build-release.sh

twine upload dist/*

git push --tags origin master

When reading from many possibly large files in a fashion similar to random access, it is usually the fastest and most efficient to use memory maps.

Although memory maps have many advantages, they represent a very limited system resource as every map uses one file descriptor, whose amount is limited per process. On 32 bit systems, the amount of memory you can have mapped at a time is naturally limited to theoretical 4GB of memory, which may not be enough for some applications.

* **System resources (file-handles) are likely to be leaked!** This is due to the library authors reliance on a deterministic `__del__()` destructor.

* The memory access is read-only by design.


Smmap wraps an interface around mmap and tracks the mapped files as well as the amount of clients who use it. If the system runs out of resources, or if a memory limit is reached, it will automatically unload unused maps to allow continued operation.

To allow processing large files even on 32 bit systems, it allows only portions of the file to be mapped. Once the user reads beyond the mapped region, smmap will automatically map the next required region, unloading unused regions using a LRU algorithm.

Although the library can be used most efficiently with its native interface, a Buffer implementation is provided to hide these details behind a simple string-like interface.

For performance critical 64 bit applications, a simplified version of memory mapping is provided which always maps the whole file, but still provides the benefit of unloading unused mappings on demand.

* Python 3.7+

* OSX, Windows or Linux

The package was tested on all of the previously mentioned configurations.

[](https://readthedocs.org/projects/smmap/?badge=latest)

Its easiest to install smmap using the [pip](http://www.pip-installer.org/en/latest) program:

$ pip install smmap

As the command will install smmap in your respective python distribution, you will most likely need root permissions to authorize the required changes.

If you have downloaded the source archive, the package can be installed by running the `setup.py` script:

$ python setup.py install

It is advised to have a look at the **Usage Guide** for a brief introduction on the different database implementations.

The project is home on github at https://github.com/gitpython-developers/smmap .

The latest source can be cloned from github as well:

* git://github.com/gitpython-developers/smmap.git

For support, please use the git-python mailing list:

* http://groups.google.com/group/git-python

Issues can be filed on github:

* https://github.com/gitpython-developers/smmap/issues

A link to the pypi page related to this repository:

* https://pypi.org/project/smmap/

*smmap* is licensed under the New BSD License.

See [GitPython](https://github.com/gitpython-developers/GitPython/blob/main/SECURITY.md). Vulnerabilities found in `smmap` can be reported there.

set -eEu

function release_with() {

$1 -m build --sdist --wheel

}

if test -n "${VIRTUAL_ENV:-}"; then

deps=(build twine) # Install twine along with build, as we need it later.

echo "Virtual environment detected. Adding packages: ${deps[*]}"

pip install --quiet --upgrade "${deps[@]}"

echo 'Starting the build.'

release_with python

function suggest_venv() {

venv_cmd='python -m venv env && source env/bin/activate'

printf "HELP: To avoid this error, use a virtual-env with '%s' instead.\n" "$venv_cmd"

}

trap suggest_venv ERR # This keeps the original exit (error) code.

echo 'Starting the build.'

release_with python3 # Outside a venv, use python3.