-
Notifications
You must be signed in to change notification settings - Fork 229
Add a warning to Introduction to Stylometry with Python (French and English); closes #1883 #1920
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
Hi @programminghistorian/technical-team ; I don't understand why this build fails; it reports broken links in three documents that I haven't changed; help please! |
|
Travis checks for URLs that are broken, and it checks the whole site - not just the pages you changed. So those are URLs that have gone down since we last built things. Even if you didn't change those pages, we generally have a policy that the person who finds the broken links fixes them as a part of the same PR. If they're not easily fixed because the resources can't be found in the past I think we've removed those links and said as much in a little emendation in the text. |
Every time we run anything, Travis looks for errors all over the site; so this is totally normal @fdlaramee :) It is weirder however that two of the links are actually working when I checked now. |
|
If that's the case you can click "re-run" next to the place where you click "build" to see the errors. I just reset. Sometimes things happen to be down temporarily when Travis runs. |
|
Things seem fine now. (and FWIW in case you went looking, it looks like the "re-run" button disappears when the travis checks pass - I swear it was there five minutes ago). |
| * Les rudiments du [Natural Language Toolkit (documentation en anglais)](https://www.nltk.org/) (nltk), un module Python populaire dédié au [traitement du langage naturel](https://fr.wikipedia.org/wiki/Traitement_automatique_du_langage_naturel). | ||
|
|
||
| <div class="alert alert-warning"> | ||
| Veuillez noter que le code informatique de cette leçon a été conçu pour être exécuté en séquence. Si, par exemple, vous désirez passer outre la méthode de Mendenhall et vous diriger directement vers celle de Klgariff ou celle de Burrows, veuillez vous assurer de copier-coller les instructions de pré-traitement qui apparaissent dans la description de la méthode de Mendenhall vers votre propre bloc de code. Sinon, vous n'obtiendrez pas exactement les résultats présentés ici. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
petite coquille dans 'Kilgariff'
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Merci @mariechristineb c'est réglé.
A user had trouble reproducing the results in the tutorial because they had skipped one of the methods and moved straight to the second or third. I added a warning that users who want to do that must make sure to copy-paste the preprocessing code from the method(s) they skip if they want to obtain the same results that I do.
Checklist
Closes #ISSUENUMBERto the description aboveIf you are having difficulty fixing Travis errors, first consult https://github.com/programminghistorian/jekyll/wiki/Making-Technical-Contributions carefully, especially "Common Travis Errors". Then contact the technical team if you need further help.