Version 0.7.1

.github/workflows/tests.yml

@@ -57,8 +57,6 @@ jobs:
              true ###############################################################
              python -m pip install --upgrade pip
              pip install -U pytest
-             pip install -Ur './requirements/requirements.txt'
-             pip install -Ur './requirements/requirements-dev.txt'
       - name: Run pytest
         run: |
              true ###############################################################

.lgtm.yml

@@ -4,8 +4,6 @@ extraction:
   python:
     python_setup:
       version: 3
-      requirements_files:
-        - requirements.txt
       setup_py: false
 
 queries:

README.md

@@ -324,8 +324,7 @@ This uses the example of editing the package on a git branch called `develop`...
 Building the ciscoconfparse2 documentation tarball comes down to this one wierd trick:
 
 - `cd sphinx-doc/`
-- `pip install -r ./requirements.txt;  # install Sphinx dependencies`
-- `pip install -r ../requirements.txt; # install ccp dependencies`
+- `pip install ciscoconfparse`
 - `make html`
 
 ## License and Copyright

pyproject.toml

@@ -2,7 +2,7 @@
 
 [project]
 name = "ciscoconfparse2"
-version = "0.7.0"
+version = "0.7.1"
 description = "Parse, Audit, Query, Build, and Modify Cisco IOS-style and JunOS-style configs"
 readme = "README.md"
 license = "GPL-3.0-only"

sphinx-doc/README.md

@@ -2,6 +2,5 @@
 Building the ccp documentation package comes down to this one wierd trick:
 
 - `cd sphinx-doc/`
-- `pip install -r ./requirements.txt;  # install Sphinx dependencies`
-- `pip install -r ../requirements.txt; # install ccp dependencies`
+- `pip install ciscoconfparse`
 - `make html`

sphinx-doc/installation.rst

@@ -16,27 +16,27 @@ Tests pass on the latest OSX without doing this, but to get ``scrypt`` to instal
 pip
 ---
 
-``pip install -U ciscoconfparse2 >= 0.6.7``
+``pip install -U ciscoconfparse2 >= 0.7.1``
 
 requirements.txt: pypi
 ----------------------
 
 If you need a direct ``pypi`` dependency entry in your ``requirements.txt``
 file, you can include an entry like this.
 
-``ciscoconfparse2 == 0.7.0``
+``ciscoconfparse2 == 0.7.1``
 
-``0.7.0`` is used only as a reference; choose the correct release for your
+``0.7.1`` is used only as a reference; choose the correct release for your
 project.
 
 requirements.txt: github
 ------------------------
 
 If you need a direct ``git`` dependency entry in your ``requirements.txt``
-file, you can include an entry like this (where ``0.6.7`` is a specific
+file, you can include an entry like this (where ``0.7.1`` is a specific
 ``git tag`` that you want to reference).
 
-``git+https://github.com/mpenning/[email protected].0``
+``git+https://github.com/mpenning/[email protected].1``
 
-``0.7.0`` is used only as a reference; choose the correct release for your
+``0.7.1`` is used only as a reference; choose the correct release for your
 project.