[EXTERNAL] fix(pandas): replace broken "Ultimate Pandas Resource" link with "Awesome Pandas" #5
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Co-authored-by: Pedro Ferreira <me.pedro.ferreira@gmail.com>
Co-authored-by: Pedro Ferreira <me.pedro.ferreira@gmail.com>
Co-authored-by: Pedro Ferreira <me.pedro.ferreira@gmail.com>
…1-edu#3047) * [EXTERNAL] fix(numpy): clarify that CSV header is excluded when loading data ### Fix ambiguous instruction about row indexing #### What changed The sentence: > "Load the data using genfromtxt, specifying the delimiter as ';', and optimize the numpy array size by reducing the data types. Use np.float32 and verify that the resulting numpy array weighs 76800 bytes." was unclear about whether the CSV header should be skipped or not. It now says: > "Load the data using genfromtxt, specifying the delimiter as ';' with excluding the headers, and optimize the numpy array size by reducing the data types. Use np.float32 and verify that the resulting numpy array weighs 76800 bytes." #### Why Later instructions refer to specific row numbers (like the 2nd, 7th, and 12th rows). Without stating whether the header counts as a row, the meaning is ambiguous — it affects the indexing. This fix makes it clear that the header should be excluded. #### No code changes This is a documentation fix only. * Revert "[EXTERNAL] fix(numpy): clarify that CSV header is excluded when loading data" --------- Co-authored-by: Abdelhak ELYakoubi <87140828+EldritchGriffin@users.noreply.github.com>
…al) (01-edu#3046) * fix(docs): correct typo in README (no → not) * Update README.md * Update README.md --------- Co-authored-by: Abdelhak ELYakoubi <87140828+EldritchGriffin@users.noreply.github.com>
…l multi-class (01-edu#3048) * [EXTERNAL] fix(numpy): clarify that CSV header is excluded when loading data ### Fix ambiguous instruction about row indexing #### What changed The sentence: > "Load the data using genfromtxt, specifying the delimiter as ';', and optimize the numpy array size by reducing the data types. Use np.float32 and verify that the resulting numpy array weighs 76800 bytes." was unclear about whether the CSV header should be skipped or not. It now says: > "Load the data using genfromtxt, specifying the delimiter as ';' with excluding the headers, and optimize the numpy array size by reducing the data types. Use np.float32 and verify that the resulting numpy array weighs 76800 bytes." #### Why Later instructions refer to specific row numbers (like the 2nd, 7th, and 12th rows). Without stating whether the header counts as a row, the meaning is ambiguous — it affects the indexing. This fix makes it clear that the header should be excluded. #### No code changes This is a documentation fix only. * docs(keras2): use categorical_crossentropy for single-label multi-class in Exercise 4 ## Summary Docs-only fix in **Keras 2 → Exercise 4 (Multi-class classification – Optimize)**: Replace the incorrect mention of `binary_crossentropy` with the correct `categorical_crossentropy` for **single-label multi-class** classification. ## Why `binary_crossentropy` is intended for **binary** or **multi-label** tasks. For **single-label multi-class** with a softmax output, the appropriate loss is **`categorical_crossentropy`**. This correction prevents learner confusion and aligns the subject with standard Keras practice. ## Scope of Change * **Updated text** in Exercise 4 to say `categorical_crossentropy` instead of `binary_crossentropy`. * Update README.md --------- Co-authored-by: Abdelhak ELYakoubi <87140828+EldritchGriffin@users.noreply.github.com>
* fixed a wrong data type given in the instructions but the expected function had it right * Fixed the main function and added an instruction --------- Co-authored-by: Pedro Ferreira <me.pedro.ferreira@gmail.com>
* fix(rust-piscine): fix checkpoint subjects * revert get_document_id state --------- Co-authored-by: Pedro Ferreira <me.pedro.ferreira@gmail.com>
student's must handle warnings Co-authored-by: Pedro Ferreira <me.pedro.ferreira@gmail.com>
Co-authored-by: Pedro Ferreira <me.pedro.ferreira@gmail.com>
* fix(chaikin): update broken link + grammar correction * fix(chaikin): fix prettier --------- Co-authored-by: Pedro Ferreira <me.pedro.ferreira@gmail.com>
Co-authored-by: Pedro Ferreira <pedro.ferreira@01talent.com>
* fix(quest-08) * fix(prettier) * fix(easy_traits): small fix on README * fix(blood_types): refine README * fix(commit_stats): apply small fix to README --------- Co-authored-by: Pedro Ferreira <pedro.ferreira@01talent.com>
Co-authored-by: Pedro Ferreira <pedro.ferreira@01talent.com>
* fix(quest-09) * fix(matrix): change link path as per repo * docs(macro_map): small refactor on MD * docs(events): small refactor for MD --------- Co-authored-by: Pedro Ferreira <pedro.ferreira@01talent.com>
### Changes - Updated outdated or broken links in documentation. - Replaced inaccessible links with correct or alternative sources. - Ensured all references are accessible and relevant to the project.
…cumentation ### Changes - Updated outdated or broken links in documentation. - Replaced inaccessible links with correct or alternative sources. - Ensured all references are accessible and relevant to the project.
Oumaimafisaoui
force-pushed
the
fix-resources-links
branch
from
d922859 to
dde3a88
Compare
… in documentation
…k with "Awesome Pandas" Thanks for catching this! The "Ultimate Pandas Resource" link was returning a 403 error. I’ve updated it to point to the actively maintained [Awesome Pandas](https://github.com/tommyod/awesome-pandas) resource instead.
Oumaimafisaoui
force-pushed
the
fix-resources-links
branch
from
6ab998e to
4565a56
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Thanks for catching this!
The "Ultimate Pandas Resource" link was returning a 403 error.
I’ve updated it to point to the actively maintained Awesome Pandas resource instead.