v1.0.0 release

Author: sertalpbilal

.coveragerc

@@ -0,0 +1,5 @@
+[report]
+exclude_lines =
+    pragma: no cover
+    pass
+precision = 2

.gitattributes

@@ -0,0 +1,11 @@
+# Exclude certain folders from release
+/doc export-ignore
+/img export-ignore
+/tests export-ignore
+.gitignore export-ignore
+.gitattributes export-ignore
+.gitlab-ci.yml export-ignore
+
+# Line endings
+*.sh text=auto eol=lf
+*.py text=auto eol=lf

.gitignore

@@ -8,6 +8,8 @@
 # Compiled files
 __pycache__/
 *.py[cod]
+*.egg-info
+dist/
 
 # Eclipse-related files
 .classpath
@@ -19,4 +21,12 @@ __pycache__/
 .buildinfo
 /doc/_build/
 /doc/generated/
+/doc/api/generated/
+/doc/savefig/
 
+# Coverage
+*.coverage*
+htmlcov/
+
+# Jupyter
+*.ipynb_checkpoints/

.gitlab-ci.yml

@@ -1,20 +1,74 @@
+
+stages:
+  - test1
+  - test2
+  - deploy
+
+default:
+  before_script:
+    - apt-get update -qq
+    - 'which ssh-agent || ( apt-get install -qq -y openssh-client )'
+    - eval $(ssh-agent -s)
+    - ssh-add <(echo "$SSH_PRIVATE_KEY")
+    - mkdir -p ~/.ssh
+    - '[[ -f /.dockerenv ]] && echo -e "Host *\n\tStrictHostKeyChecking no\n\n" > ~/.ssh/config'
+    - scp $CASCOPY ~/
+
+py36:
+  stage: test1
+  image: python:3.6
+  script:
+  - python setup.py install
+  - pip install coverage
+  - cd tests
+  - ./test_coverage.sh
+
 py37:
+  stage: test2
   image: python:3.7
   script:
   - python setup.py install
+  - pip install coverage
   - cd tests
-  - python test_generators.py
+  - ./test_coverage.sh
 
-#py36:
-#  image: python:3.6
-#  script:
-#  - python setup.py install
-#  - cd tests
-#  - python test_generators.py
-#
-#py35:
-#  image: python:3.5
-#  script:
-#  - python setup.py install
-#  - cd tests
-#  - python test_generators.py
+push_to_pypi:
+  image: python:latest
+  stage: deploy
+  before_script:
+    - apt-get update -qq
+  script:
+    - python -m pip install --upgrade setuptools wheel
+    - python setup.py sdist bdist_wheel
+    - python -m pip install --upgrade twine
+    - echo $PYPI_URL
+    - python -m twine upload --skip-existing -u __token__ -p $PYPI_TOKEN --repository-url $PYPI_URL dist/*
+  when: manual
+
+push_to_conda:
+  image: python:latest
+  stage: deploy
+  before_script:
+    - apt-get update -qq
+    - wget https://repo.continuum.io/miniconda/Miniconda3-latest-Linux-x86_64.sh -O miniconda.sh
+    - bash miniconda.sh -b -p $HOME/miniconda
+    - PATH=$PATH:$HOME/miniconda/bin
+    - conda config --set always_yes yes
+    - conda config --add channels conda-forge
+    - conda config --add channels sas-institute
+    - conda install conda-build
+    - conda update -n base -c defaults conda
+    - conda install anaconda-client
+    - conda install conda-verify
+    - mkdir build
+  script:
+    - conda build -c conda-forge -c sas-institute --output-folder build/ --python 3.6 conda/
+    - conda build -c conda-forge -c sas-institute --output-folder build/ --python 3.7 conda/
+    - cd build
+    - conda convert -p all `ls linux-64/*-py3*.tar.bz2`
+    - anaconda -t $ANACONDA_TOKEN upload -u sas-institute --force `ls linux-64/*-py3*.tar.bz2`
+    - anaconda -t $ANACONDA_TOKEN upload -u sas-institute --force `ls linux-32/*-py3*.tar.bz2`
+    - anaconda -t $ANACONDA_TOKEN upload -u sas-institute --force `ls win-32/*-py3*.tar.bz2`
+    - anaconda -t $ANACONDA_TOKEN upload -u sas-institute --force `ls win-64/*-py3*.tar.bz2`
+    - anaconda -t $ANACONDA_TOKEN upload -u sas-institute --force `ls osx-64/*-py3*.tar.bz2`
+  when: manual

CONTRIBUTING.md

@@ -0,0 +1,65 @@
+# Contributing to sasoptpy
+
+We welcome all contributions including bug reports, new features,
+documentation fixes, performance enchancements, and new ideas.
+
+## Submitting a Pull Request
+
+If you have a contribution to make, submit a pull request using GitHub.
+You need to add a unit test for any source code changes, including bug fixes.
+Except for minor fixes, pull requests that do not have a unit test will not be accepted.
+If your change drops the code coverage, you may be asked to write additional
+unit tests.
+
+You must include the text from the ContributerAgreement.txt file
+along with your sign-off verifying that the change originated from you.
+
+## Testing
+
+Python [unittest](https://docs.python.org/3/library/unittest.html) are used for testing sasoptpy.
+
+Automated testing is performed using GitLab for internal development,
+but you can run unit tests in a Python environment.
+
+In order to run all the tests, you need to have certain environment variables set:
+
+* CAS Environment Variables:
+  * __CASHOST__: Host or IP address for CAS sessions
+  * __CASPORT__: Port number for CAS session
+  * __AUTHINFO__: The location of your `.authinfo` file, that includes your username and password
+  * __CASUSERNAME__: User name for the CAS session. This is required if `AUTHINFO` does not exist.
+  * __CASPASSWORD__: Password for the CAS session. This is required if `AUTHINFO` does not exist.
+* SAS Environment Variables:
+  * __SASHOST__: Host or IP address for SAS installation
+  * __SASPATH__: Absolute path of the SAS installation in the host
+
+The CAS server should be active at runtime.
+
+You can start running all the unit tests under `tests` folder as follows:
+
+``` shell
+python -m unittest discover -s tests/ -p 'test*.py'
+```
+
+If you install `coverage` package, you can see the total coverage of the unit tests.
+Under `tests` you can run `test_coverage.sh` (or `test_coverage.bat`) to see the final coverage.
+HTML pages will be created under `tests/html` folder.
+
+## Documentation
+
+The sasoptpy documentation is generated using [Sphinx](https://www.sphinx-doc.org/en/master/).
+Documentation is generated in both HTML (for web view) and LaTeX (for PDF file) formats.
+
+Sphinx handles both function APIs using the source files and Markdown files under `doc` folder.
+Configuration for Sphinx can be found under `doc/conf.py` file.
+A script is available for generating both formats `doc/makedocs.sh`.
+
+Final sasoptpy documentation is generated using a script at
+
+https://github.com/sertalpbilal/sasoptpy_doc_generator
+
+You can generate the multi-version documentation pages using [`generate_latest.sh`](https://github.com/sertalpbilal/sasoptpy_doc_generator/blob/master/generate_latest.sh) script, found
+in the repository.
+
+A [docker image](https://hub.docker.com/r/sertalpbilal/sphinx_dev/dockerfile) is available at Docker Hub
+that includes all dependencies.

ContributorAgreement.txt

@@ -0,0 +1,56 @@
+Contributor Agreement
+
+Version 1.1
+
+Contributions to this software are accepted only when they are
+properly accompanied by a Contributor Agreement. The Contributor
+Agreement for this software is the Developer's Certificate of Origin
+1.1 (DCO) as provided with and required for accepting contributions
+to the Linux kernel.
+
+In each contribution proposed to be included in this software, the
+developer must include a "sign-off" that denotes consent to the
+terms of the Developer's Certificate of Origin.  The sign-off is
+a line of text in the description that accompanies the change,
+certifying that you have the right to provide the contribution
+to be included.  For changes provided in source code control (for
+example, via a Git pull request) the sign-off must be included in
+the commit message in source code control.  For changes provided
+in email or issue tracking, the sign-off must be included in the
+email or the issue, and the sign-off will be incorporated into the
+permanent commit message if the contribution is accepted into the
+official source code.
+
+If you can certify the below:
+
+        Developer's Certificate of Origin 1.1
+
+        By making a contribution to this project, I certify that:
+
+        (a) The contribution was created in whole or in part by me and I
+            have the right to submit it under the open source license
+            indicated in the file; or
+
+        (b) The contribution is based upon previous work that, to the best
+            of my knowledge, is covered under an appropriate open source
+            license and I have the right under that license to submit that
+            work with modifications, whether created in whole or in part
+            by me, under the same open source license (unless I am
+            permitted to submit under a different license), as indicated
+            in the file; or
+
+        (c) The contribution was provided directly to me by some other
+            person who certified (a), (b) or (c) and I have not modified
+            it.
+
+        (d) I understand and agree that this project and the contribution
+            are public and that a record of the contribution (including all
+            personal information I submit with it, including my sign-off) is
+            maintained indefinitely and may be redistributed consistent with
+            this project or the open source license(s) involved.
+
+then you just add a line saying
+
+        Signed-off-by: Random J Developer <[email protected]>
+
+using your real name (sorry, no pseudonyms or anonymous contributions.)

MANIFEST.in

@@ -0,0 +1 @@
+global-include *.py