profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/cpagravel/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.

sergei1152/TrussSim.js 4

A general purpose 2D Truss Simulator/Optimizer

cpagravel/asteroids 2

The Asteroids game on an ARM Cortex M4

cpagravel/gst 2

Git status tool for Bash

cpagravel/asteroids.js 0

Asteroids made in Javascript to learn about gamestate handling.

cpagravel/cdb 0

Bookmark tool for command line navigation

cpagravel/EasyClangComplete 0

C/C++ autocompletion in Sublime Text 3 for human beings

cpagravel/gst-python 0

Python port of gst for cross platform compatibility

cpagravel/py-faster-rcnn 0

Faster R-CNN (Python implementation) -- see https://github.com/ShaoqingRen/faster_rcnn for the official MATLAB version

cpagravel/pylibftdi 0

Minimal pythonic wrapper to Intra2net's libftdi driver for FTDI's USB devices

push eventcpagravel/randomness_testsuite

Chris Gravel

commit sha 90576ed92c6cdafc34658fc2b1e159fdb5b0fa66

Bump version to 0.2.0

view details

push time in 16 days

push eventcpagravel/randomness_testsuite

Chris Gravel

commit sha f9b04dd797cc17ecf77cad5b528b0160c7b57bb9

Bump version to 0.2.0

view details

push time in 17 days

push eventcpagravel/randomness_testsuite

Chris Gravel

commit sha deca4fa6c83fbabf44e8d109d0056f2ddebfb5dd

Code cleanup - Make return type consistent, fix imports, and... Fix alignment in test functions. Remove extra import calls. Make all return types consistent as List[Tuple[name, score, pass/fail]]

view details

Chris Gravel

commit sha 7285843dcc0ea9ed14bd0a526e7d6f977bb3f8cd

Bump version to 0.2.0

view details

push time in 17 days

push eventcpagravel/randomness_testsuite

Chris Gravel

commit sha 42b1d61b7bd65fb9088f3790acdea322ec09b221

Create package for distribution

view details

push time in 17 days

startedcpagravel/gst-python

started time in 17 days

push eventcpagravel/randomness_testsuite

Chris Gravel

commit sha 12f81d7d734678beeb1f40ad9f53919bb3bea862

Create package for distribution

view details

push time in 17 days

push eventcpagravel/randomness_testsuite

Steven Kho Ang

commit sha bad26f70b8b23b5bdcce1155482ddd0c4023f913

Merge pull request #5 from cpagravel/master Fix typo sepctral_test -> spectral_test

view details

push time in 17 days

PR opened stevenang/randomness_testsuite

Fix typo sepctral_test -> spectral_test

Saw a typo I wanted to fix. Used search and replace to get all instances.

+9 -9

0 comment

9 changed files

pr created time in 17 days

push eventcpagravel/randomness_testsuite

Chris Gravel

commit sha f65b6f62f7ae28d9414798f812903ceaa2303982

Fix typo sepctral_test -> spectral_test

view details

push time in 17 days

fork cpagravel/randomness_testsuite

This is a Python implementation of NIST's A Statistical Test Suite for Random and Pseudorandom Number Generators for Cryptographic Applications

fork in 17 days

issue openedgoogle/mobly

Why does mobly use the root logger?

Isn't use of the root logger bad practice? I'll quote the Python documentation for libraries (https://docs.python.org/3/howto/logging.html#configuring-logging-for-a-library)

Note It is strongly advised that you do not add any handlers other than NullHandler to your library’s loggers. This is because the configuration of handlers is the prerogative of the application developer who uses your library. The application developer knows their target audience and what handlers are most appropriate for their application: if you add handlers ‘under the hood’, you might well interfere with their ability to carry out unit tests and deliver logs which suit their requirements.

Using the root logger will call basicConfig and subsequently add handlers to the root logger which is undesirable for an application developer who wants to control the logging for their requirements.

created time in 2 months