If you are wondering where the data of this site comes from, please visit 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.

nmstoker/lockebot 91

LockeBot: a demonstration of implementing a basic question answering bot with use of Rasa and a database

nmstoker/MultiLingualBot 11

MultiLingualBot: a simple multi-lingual bot that can respond to questions on academic subjects

nmstoker/gatherup 8

Helps you post essential Python config details to GitHub or Discourse, all beautifully formatted

nmstoker/normalise 1

A module for normalising text.

nmstoker/open-speech-corpora 1

A list of accessible speech corpora for ASR, TTS, and other Speech Technologies

nmstoker/PyShortTextCategorization 1

Various Algorithms for Short Text Categorization

nmstoker/acl2017-non-factoid-qa 0

Code for paper "End-to-End Non-Factoid Question Answering with an Interactive Visualization of Neural Attention Weights"

nmstoker/afraid-to-commit 0

Don't be afraid to commit - a workshop/tutorial for inexperienced Python/Django developers who would like to contribute more to the projects they use.

nmstoker/cmudict-tools 0

Tools for working with the CMU Pronunciation Dictionary

nmstoker/deep-text-correcter 0

Deep learning models trained to correct input errors in short, message-like text

issue openedpyccel/pyccel

Update docs to give details of comparative speed advantage

The documentation goes into excellent detail about what to do, but skips over the why, giving no motivation.

Presumably it's expected to be much faster than regular Python and to a degree faster than things like Numpy, but there is no mention of this or what approximate factor of speed improvement one might realistically expect.

Could a quick comparison be given?

created time in 2 days


started time in 2 days


started time in 8 days


started time in 9 days

issue commentjupyter-widgets/ipywidgets

Playing an Audio widget programmatically?

My autoplay method is clunky and won't give the kind of control that lets you stop playback, but it would work to trigger playback programmatically if you didn't mind the side effects.

Generally speaking though a better solution (eg with widget code /use of web audio API as you mention) seems the smarter way to go, but I don't know if there's any progress there


comment created time in 10 days


started time in 16 days


started time in 17 days


started time in a month


started time in a month


started time in a month


started time in a month


started time in a month


started time in a month


started time in a month


started time in a month

issue commentasweigart/pyautogui


@nickpythonluajava I saw you'd also posted this in PyDirectInput:

So ideally you should:

  1. Close this issue (as I mentioned above it's not relevent to this repo)
  2. Answer your own issue using the explanation given here about the order of the down and up keys (ie doing all down keys first and then the up keys) and then when you've written it up, you can close that issue too Hope the original advice above was useful, I'm pretty sure that the order is your problem.

comment created time in a month

issue commentasweigart/pyautogui

Re-publish the docs

Hi @asweigart - am guessing you're busy. Is there a way others can push the docs update to ReadTheDocs for the above points?


comment created time in a month


started time in 2 months


started time in 2 months

issue commentasweigart/pyautogui


As you are using another module (import pydirectinput) it looks to me like this isn't directly related to PyAutoGUI and you'd do better to go to the repo for that module or Google it.

However if pydirectinput works like PtAutoGUI's own press function then it's expected that it will be pressing them one at a time because the press corresponds to a key up then a key down, so your code effectively let's go of the first key then moves on to the next.

If you want multiple keys at once you need to send the key downs all together and then the key ups all together (for the keys you want pressed at the same time at least)


comment created time in 2 months


started time in 2 months


started time in 2 months

issue commentasweigart/pyautogui

Re-publish the docs

Doing this would resolve the (fixed) source of confusion behind #357 too

The long outdated reference to Ubuntu problems with Pillow is also resolved in the repo docs, just not in the actually published ones, eg here:


comment created time in 2 months

issue openedasweigart/pyautogui

Re-publish the docs

Thank you for this great repo.

I happened to notice that someone kindly fixed an out of date mention in the repo docs of Python 3.8 not being supported by Pillow (which is definitely no longer the case as it supports 3.9 already with an issue open for 3.10) thanks to the PR here:

However it seems that despite the repo docs being fine now, the published docs are still not reflecting the change. I don't know for sure how you've got them set up but I'm guessing it simply needed someone to push a re-publishing of the docs for it to pull the latest text from the repo and everything will then be consistent.

What's currently published:

What's in the repo:

created time in 2 months

issue commentdavisking/dlib

Installation failed on zorin os 15.3

Maybe I've misunderstood you @rinkeshpanwar but it looks like either:

  1. you could be misunderstanding the point about the python headers (what you write suggests you might not know about how the Python headers work: you don't import them into python, they're usually an OS level package you install)
  2. you could be running into a similar problem to #1269 whereby you need to create your virtual environment after you install the headers

Anyway, I'd start by trying:

sudo apt install python3.6-dev

If option 2 above applies, recreate your virtual env. Then try again.


comment created time in 2 months


started time in 2 months


started time in 2 months


started time in 2 months


started time in 2 months

issue commentespeak-ng/espeak-ng

modifying the intonations file

Thanks @jaacoppi

That documentation is great for giving a formal definition of the pieces that make up a tune, but it seems a little hard to relate to what they really mean and how that affects the output.

How about I take a closer look over the next few days and give further feedback then? It might just be that I need to jump into it and I can figure things out by experimenting and a bit more effort on my part.

Maybe @joshknnd1982 can add what they're after that's not covered too?


comment created time in 2 months