amaranth/setup.py
whitequark 6e1145e2e7 setup: tighten version constraint on Jinja2.
I remember thinking that not constraining it properly might bite us
someday, but assumed that Jinja2 will always stay version 2. Now it
looks like Jinja2 3.0.0a1 got released, pip picks it by default, and
it's currently broken (something about markupsafe missing).

Do what needed to be done in the first place.
2020-04-02 01:35:39 +00:00

44 lines
1.2 KiB
Python

from setuptools import setup, find_packages
def scm_version():
def local_scheme(version):
if version.tag and not version.distance:
return version.format_with("")
else:
return version.format_choice("+{node}", "+{node}.dirty")
return {
"relative_to": __file__,
"version_scheme": "guess-next-dev",
"local_scheme": local_scheme
}
setup(
name="nmigen",
use_scm_version=scm_version(),
author="whitequark",
author_email="whitequark@whitequark.org",
description="Python toolbox for building complex digital hardware",
#long_description="""TODO""",
license="BSD",
python_requires="~=3.6",
setup_requires=["setuptools_scm"],
install_requires=[
"setuptools",
"pyvcd~=0.1.4", # for nmigen.pysim
"Jinja2~=2.11", # for nmigen.build
],
packages=find_packages(),
entry_points={
"console_scripts": [
"nmigen-rpc = nmigen.rpc:main",
]
},
project_urls={
#"Documentation": "https://nmigen.readthedocs.io/",
"Source Code": "https://github.com/nmigen/nmigen",
"Bug Tracker": "https://github.com/nmigen/nmigen/issues",
},
)