If you wish to contact the PyGaze developers, please keep in mind that we are only human. We try our best to provide you with the best possible package and we are very open to feedback (keep it classy, though), but we’re pretty busy too. Although we appreciate your input and we will try our very best to answer your questions as quick as possible, sometimes replying might take a bit of time. Thanks in advance for your patience and understanding!


We sure hope you won’t come across any bugs, but if you do, you’re always welcome to report them via the GitHub Issue Page. If you’re up to it, any help with fixing the bugs is welcome too. You can always fork the GitHub repository and commit fixes. If you prefer to work via different channels (the support forum, or our contact form below, or via carrier pigeon), that’s fine too. If you help us fix something, we promise you’ll get an honorary mention in our Hall of Fame.

Feature requests

If you miss something in PyGaze and would like to see it added, you could file a feature request. Like bugs, feature requests may be filed via the GitHub Issue Page and you’re very welcome to fork the GitHub repository and commit new stuff. Creating new functionality yourself will result in an honorary mention in our Hall of Fame. If you don’t have a GitHub account, rest assured: new features can be requested via the support forum or the contact form as well.

Support forum

A very nice and direct way of giving feedback or asking for help, is to post a new thread on our support forum. The PyGaze developers will try to closely monitor the forum, and answer all your questions as soon as possible. Please note that you are required to register an account before you can post. This is entirely free, though, and your email will not be used to send you stuff you do not want. Of course, browsing the existing threads on the forum does not require registration, and might prove very helpful!


If you feel the need to tell us something and don’t want to register on GitHub or the forum, you can email Edwin at

Comments are closed