Latest Threat Research:SANDWORM_MODE: Shai-Hulud-Style npm Worm Hijacks CI Workflows and Poisons AI Toolchains.Details
Socket
Book a DemoInstallSign in
Socket

palace

Package Overview
Dependencies
Maintainers
3
Versions
21
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

palace - npm Package Compare versions

Comparing version
0.2.4
to
0.2.5
+18
docs/gitlab-ci.yml
image: python:slim
before_script:
- apt-get update
- apt-get install -y git cmake build-essential libopenal-dev
- git clone https://github.com/kcat/alure
- cmake -DCMAKE_INSTALL_PREFIX:PATH=/usr -S alure -B alure/build
- cmake --build alure/build --parallel `nproc` --target install
- rm -fr alure
pages:
stage: deploy
script:
- python -m pip install Sphinx pydata-sphinx-theme .
- sphinx-build -bhtml docs/source public
artifacts:
paths:
- public
only:
- main
[:python_version < "3.8"]
typing-extensions
+7
-4

@@ -11,3 +11,3 @@ # Configuration file for the Sphinx documentation builder.

author = 'Nguyễn Gia Phong et al.'
release = '0.2.4'
release = '0.2.5'

@@ -17,4 +17,3 @@ # Add any Sphinx extension module names here, as strings.

# or your custom ones.
extensions = [
'sphinx.ext.autodoc', 'sphinx.ext.githubpages', 'sphinx.ext.napoleon']
extensions = ['sphinx.ext.autodoc', 'sphinx.ext.napoleon']
napoleon_google_docstring = False

@@ -32,3 +31,7 @@ default_role = 'py:obj'

# Options for HTML output
html_theme = 'sphinx_rtd_theme'
html_theme = 'pydata_sphinx_theme'
html_theme_options = {'external_links': [
{'name': 'SourceHut', 'url': 'https://sr.ht/~cnx/palace'},
{'name': 'PyPI', 'url': 'https://pypi.org/project/palace'},
{'name': 'Matrix', 'url': 'https://matrix.to/#/#palace-dev:matrix.org'}]}

@@ -35,0 +38,0 @@ # Add any paths that contain custom static files (such as style sheets)

Getting Involved
================
.. currentmodule:: palace
First of all, thank you for using and contributing to palace! We welcome

@@ -94,7 +96,186 @@ all forms of contribution, and `the mo the merier`_. By saying this, we also

Style Guidelines
Coding Standards
----------------
Philosophy
^^^^^^^^^^
In order to write safe, efficient, easy-to-use and extendable Python,
the following principals should be followed.
.. _impl-idiom:
The Impl Idiom
""""""""""""""
*Not to be confused with* `the pimpl idiom`_.
For memory-safety, whenever possible, we rely on Cython for allocation and
deallocation of C++ objects. To do this, the nullary constructor needs to be
(re-)declared in Cython, e.g.
.. code-block:: cython
cdef extern from 'foobar.h' namespace 'foobar':
cdef cppclass Foo:
Foo()
float meth(size_t crack) except +
...
The Cython extension type can then be declared as follows
.. code-block:: cython
cdef class Bar:
cdef Foo impl
def __init__(self, *args, **kwargs):
self.impl = ...
@staticmethod
def from_baz(baz: Baz) -> Bar:
bar = Bar.__new__(Bar)
bar.impl = ...
return bar
def meth(self, crack: int) -> float:
return self.impl.meth(crack)
The Modern Python
"""""""""""""""""
One of the goal of palace is to create a Pythonic, i.e. intuitive and concise,
interface. To achieve this, we try to make use of some modern Python features,
which not only allow users to adopt palace with ease, but also make their
programs more readable and less error-prone.
.. _getter-setter:
Property Attributes
'''''''''''''''''''
A large proportion of alure API are getters/setter methods. In Python,
it is a good practice to use property_ to abstract these calls, and thus make
the interface more natural with attribute-like referencing and assignments.
Due to implementation details, Cython has to hijack the ``@property`` decorator
to make it work for read-write properties. Unfortunately, the Cython-generated
descriptors do not play very well with other builtin decorators, thus in some
cases, it is recommended to alias the call to ``property`` as follows
.. code-block:: python
getter = property
setter = lambda fset: property(fset=fset, doc=fset.__doc__)
Then ``@getter`` and ``@setter`` can be used to decorate read-only and
write-only properties, respectively, without any trouble even if other
decorators are used for the same extension type method.
Context Managers
''''''''''''''''
The alure API defines many objects that need manual tear-down in
a particular order. Instead of trying to be clever and perform automatic
clean-ups at garbage collection, we should put the user in control.
To quote *The Zen of Python*,
| If the implementation is hard to explain, it's a bad idea.
| If the implementation is easy to explain, it may be a good idea.
With that being said, it does not mean we do not provide any level of
abstraction. A simplified case in point would be
.. code-block:: cython
cdef class Device:
cdef alure.Device impl
def __init__(self, name: str = '') -> None:
self.impl = devmgr.open_playback(name)
def __enter__(self) -> Device:
return self
def __exit__(self, *exc) -> Optional[bool]:
self.close()
def close(self) -> None:
self.impl.close()
Now if the ``with`` statement is used, it will make sure the device
will be closed, regardless of whatever may happen within the inner block
.. code-block:: python
with Device() as dev:
...
as it is equivalent to
.. code-block:: python
dev = Device()
try:
...
finally:
dev.close()
Other than closure/destruction of objects, typical uses of `context managers`__
also include saving and restoring various kinds of global state (as seen in
:py:class:`Context`), locking and unlocking resources, etc.
__ https://docs.python.org/3/reference/datamodel.html#context-managers
The Double Reference
''''''''''''''''''''
While wrapping C++ interfaces, :ref:`the impl idiom <impl-idiom>` might not
be adequate, since the derived Python methods need to be callable from C++.
Luckily, Cython can handle Python objects within C++ classes just fine,
although we'll need to handle the reference count ourselves, e.g.
.. code-block:: cython
cdef cppclass CppDecoder(alure.BaseDecoder):
Decoder pyo
__init__(Decoder decoder):
this.pyo = decoder
Py_INCREF(pyo)
__dealloc__():
Py_DECREF(pyo)
bool seek(uint64_t pos):
return pyo.seek(pos)
With this being done, we can now write the wrapper as simply as
.. code-block:: cython
cdef class BaseDecoder:
cdef shared_ptr[alure.Decoder] pimpl
def __cinit__(self, *args, **kwargs) -> None:
self.pimpl = shared_ptr[alure.Decoder](new CppDecoder(self))
def seek(pos: int) -> bool:
...
Because ``__cinit__`` is called by ``__new__``, any Python class derived
from ``BaseDecoder`` will be exposed to C++ as an attribute of ``CppDecoder``.
Effectively, this means the users can have the alure API calling their
inherited Python object as naturally as if palace is implemented in pure Python.
In practice, :py:class:`BaseDecoder` will also need to take into account
other guarding mechanisms like :py:class:`abc.ABC`. Due to Cython limitations,
implementation as a pure Python class and :ref:`aliasing <getter-setter>` of
``@getter``/``@setter`` should be considered.
Style Guidelines
^^^^^^^^^^^^^^^^
Python and Cython
^^^^^^^^^^^^^^^^^
"""""""""""""""""

@@ -123,3 +304,3 @@ Generally, palace follows :pep:`8` and :pep:`257`,

C++
^^^
"""

@@ -129,3 +310,3 @@ C++ codes should follow GNU style, which is best documented at Octave_.

reStructuredText
^^^^^^^^^^^^^^^^
""""""""""""""""

@@ -163,4 +344,6 @@ Overall, palace's documentation follows CPython documenting_ style guide,

.. _twine: https://twine.readthedocs.io
.. _the pimpl idiom: https://wiki.c2.com/?PimplIdiom
.. _property: https://docs.python.org/3/library/functions.html#property
.. _numpydoc: https://numpydoc.readthedocs.io/en/latest/format.html
.. _Octave: https://wiki.octave.org/C%2B%2B_style_guide
.. _documenting: https://devguide.python.org/documenting/#style-guide

@@ -23,14 +23,5 @@ Overview

reference/index
design
contributing
copying
.. toctree::
:caption: Quick Navigation
:hidden:
SourceHut Project <https://sr.ht/~cnx/palace>
Python Package Index <https://pypi.org/project/palace>
Matrix Chat Room <https://matrix.to/#/#palace-dev:matrix.org>
Indices and Tables

@@ -37,0 +28,0 @@ ------------------

Metadata-Version: 2.1
Name: palace
Version: 0.2.4
Version: 0.2.5
Summary: Pythonic Audio Library and Codecs Environment
Home-page: https://mcsinyx.gitlab.io/palace
Author: Nguyễn Gia Phong
Author-email: mcsinyx@disroot.org
Author-email: ~cnx/palace@lists.sr.ht
License: LGPLv3+

@@ -77,3 +77,3 @@ Description: # palace

[list]: https://lists.sr.ht/~cnx/palace
[API]: https://mcsinyx.gitlab.io/palace/reference.html
[API]: https://mcsinyx.gitlab.io/palace/reference/index.html
[contrib]: https://mcsinyx.gitlab.io/palace/contributing.html

@@ -80,0 +80,0 @@ [design]: https://mcsinyx.gitlab.io/palace/design.html

@@ -9,3 +9,5 @@ CMakeLists.txt

tox.ini
/home/cnx/Salsa/games/palace/src/palace.cpp
docs/Makefile
docs/gitlab-ci.yml
docs/make.bat

@@ -15,3 +17,2 @@ docs/source/conf.py

docs/source/copying.rst
docs/source/design.rst
docs/source/index.rst

@@ -43,6 +44,6 @@ docs/source/installation.rst

palace.egg-info/not-zip-safe
palace.egg-info/requires.txt
palace.egg-info/top_level.txt
src/alure.pxd
src/bases.h
src/palace.cpp
src/palace.pyx

@@ -49,0 +50,0 @@ src/std.pxd

Metadata-Version: 2.1
Name: palace
Version: 0.2.4
Version: 0.2.5
Summary: Pythonic Audio Library and Codecs Environment
Home-page: https://mcsinyx.gitlab.io/palace
Author: Nguyễn Gia Phong
Author-email: mcsinyx@disroot.org
Author-email: ~cnx/palace@lists.sr.ht
License: LGPLv3+

@@ -77,3 +77,3 @@ Description: # palace

[list]: https://lists.sr.ht/~cnx/palace
[API]: https://mcsinyx.gitlab.io/palace/reference.html
[API]: https://mcsinyx.gitlab.io/palace/reference/index.html
[contrib]: https://mcsinyx.gitlab.io/palace/contributing.html

@@ -80,0 +80,0 @@ [design]: https://mcsinyx.gitlab.io/palace/design.html

@@ -69,3 +69,3 @@ # palace

[list]: https://lists.sr.ht/~cnx/palace
[API]: https://mcsinyx.gitlab.io/palace/reference.html
[API]: https://mcsinyx.gitlab.io/palace/reference/index.html
[contrib]: https://mcsinyx.gitlab.io/palace/contributing.html

@@ -72,0 +72,0 @@ [design]: https://mcsinyx.gitlab.io/palace/design.html

[metadata]
name = palace
version = 0.2.4
version = 0.2.5
url = https://mcsinyx.gitlab.io/palace
author = Nguyễn Gia Phong
author_email = mcsinyx@disroot.org
author_email = ~cnx/palace@lists.sr.ht
classifiers =

@@ -32,2 +32,4 @@ Development Status :: 4 - Beta

python_requires = >=3.6
install_requires =
typing-extensions; python_version < '3.8'

@@ -34,0 +36,0 @@ [egg_info]

Design Principles
=================
.. currentmodule:: palace
In this section, we will discuss a few design principles in order to write
a safe, efficient, easy-to-use and extendable 3D audio library for Python,
by wrapping existing functionalities from the C++ API alure_.
This part of the documentation assumes its reader are at least familiar with
Cython, Python and C++11.
.. _impl-idiom:
The Impl Idiom
--------------
*Not to be confused with* `the pimpl idiom`_.
For memory-safety, whenever possible, we rely on Cython for allocation and
deallocation of C++ objects. To do this, the nullary constructor needs to be
(re-)declared in Cython, e.g.
.. code-block:: cython
cdef extern from 'foobar.h' namespace 'foobar':
cdef cppclass Foo:
Foo()
float meth(size_t crack) except +
...
The Cython extension type can then be declared as follows
.. code-block:: cython
cdef class Bar:
cdef Foo impl
def __init__(self, *args, **kwargs):
self.impl = ...
@staticmethod
def from_baz(baz: Baz) -> Bar:
bar = Bar.__new__(Bar)
bar.impl = ...
return bar
def meth(self, crack: int) -> float:
return self.impl.meth(crack)
The Modern Python
-----------------
One of the goal of palace is to create a Pythonic, i.e. intuitive and concise,
interface. To achieve this, we try to make use of some modern Python features,
which not only allow users to adopt palace with ease, but also make their
programs more readable and less error-prone.
.. _getter-setter:
Property Attributes
^^^^^^^^^^^^^^^^^^^
A large proportion of alure API are getters/setter methods. In Python,
it is a good practice to use property_ to abstract these calls, and thus make
the interface more natural with attribute-like referencing and assignments.
Due to implementation details, Cython has to hijack the ``@property`` decorator
to make it work for read-write properties. Unfortunately, the Cython-generated
descriptors do not play very well with other builtin decorators, thus in some
cases, it is recommended to alias the call to ``property`` as follows
.. code-block:: python
getter = property
setter = lambda fset: property(fset=fset, doc=fset.__doc__)
Then ``@getter`` and ``@setter`` can be used to decorate read-only and
write-only properties, respectively, without any trouble even if other
decorators are used for the same extension type method.
Context Managers
^^^^^^^^^^^^^^^^
The alure API defines many objects that need manual tear-down in
a particular order. Instead of trying to be clever and perform automatic
clean-ups at garbage collection, we should put the user in control.
To quote *The Zen of Python*,
| If the implementation is hard to explain, it's a bad idea.
| If the implementation is easy to explain, it may be a good idea.
With that being said, it does not mean we do not provide any level of
abstraction. A simplified case in point would be
.. code-block:: cython
cdef class Device:
cdef alure.Device impl
def __init__(self, name: str = '') -> None:
self.impl = devmgr.open_playback(name)
def __enter__(self) -> Device:
return self
def __exit__(self, *exc) -> Optional[bool]:
self.close()
def close(self) -> None:
self.impl.close()
Now if the ``with`` statement is used, it will make sure the device
will be closed, regardless of whatever may happen within the inner block
.. code-block:: python
with Device() as dev:
...
as it is equivalent to
.. code-block:: python
dev = Device()
try:
...
finally:
dev.close()
Other than closure/destruction of objects, typical uses of `context managers`__
also include saving and restoring various kinds of global state (as seen in
:py:class:`Context`), locking and unlocking resources, etc.
__ https://docs.python.org/3/reference/datamodel.html#context-managers
The Double Reference
--------------------
While wrapping C++ interfaces, :ref:`the impl idiom <impl-idiom>` might not
be adequate, since the derived Python methods need to be callable from C++.
Luckily, Cython can handle Python objects within C++ classes just fine,
although we'll need to handle the reference count ourselves, e.g.
.. code-block:: cython
cdef cppclass CppDecoder(alure.BaseDecoder):
Decoder pyo
__init__(Decoder decoder):
this.pyo = decoder
Py_INCREF(pyo)
__dealloc__():
Py_DECREF(pyo)
bool seek(uint64_t pos):
return pyo.seek(pos)
With this being done, we can now write the wrapper as simply as
.. code-block:: cython
cdef class BaseDecoder:
cdef shared_ptr[alure.Decoder] pimpl
def __cinit__(self, *args, **kwargs) -> None:
self.pimpl = shared_ptr[alure.Decoder](new CppDecoder(self))
def seek(pos: int) -> bool:
...
Because ``__cinit__`` is called by ``__new__``, any Python class derived
from ``BaseDecoder`` will be exposed to C++ as an attribute of ``CppDecoder``.
Effectively, this means the users can have the alure API calling their
inherited Python object as naturally as if palace is implemented in pure Python.
In practice, :py:class:`BaseDecoder` will also need to take into account
other guarding mechanisms like :py:class:`abc.ABC`. Due to Cython limitations,
implementation as a pure Python class and :ref:`aliasing <getter-setter>` of
``@getter``/``@setter`` should be considered.
.. _alure: https://github.com/kcat/alure
.. _`the pimpl idiom`: https://wiki.c2.com/?PimplIdiom
.. _property: https://docs.python.org/3/library/functions.html#property

Sorry, the diff of this file is too big to display

Sorry, the diff of this file is too big to display