Timothy Brathwaite
Timothy Brathwaite
Hi @itamarst, thanks for this great package! I've recently gotten interested in using Eliot, especially in using it programmatically and through Jupyter notebooks. I saw [here](https://pythonspeed.com/articles/logging-for-scientific-computing/) in the "The future:...
# Request Currently, PyLogit is built atop `numpy` and `scipy.sparse` for computational of choice probabilities, gradients, and hessians. This computational backend has at least two problems. 1. It restricts us...
Create or find an automated way to update contributors.rst based on the merged pull requests or git commit record of the develop branch. For instance, I need to add danphan...
# What This package is missing a CONTRIBUTING.md file. Contributors therefore start without clarity on how to: - begin - understand pylogit internals - set up their development environment -...
# What Currently, the README references both the `conda-forge` and the `timothyb0912` anaconda channels. Given that I didn't get the conda skeleton build to succeed for my personal channel, I...
# Request Create online documentation as in a readthedocs page or [something similar](https://docusaurus.io/).
# Request The current codebase should be substantially simplified and clarified. There are a number of code smells (e.g. mega classes with no separation of concerns), and the codebase could...
# Request Create a wiki page on the repo that describes (in detail) the steps to be performed before releasing a new version of PyLogit to PyPI and Conda. Should...
# Request Make use of static analysis tasks such as monitoring code complexity, test coverage, etc. happen on every pull request. See tools like [radon](complexity) for measuring code complexity.
# Request To improve code quality and consistency, add pre-commit hooks such as - isort / reorder-python-imports - flake8 - black