Skip to content
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

crypto_hist.set_index("time") raises KeyError(f"None of {missing} are in the columns") #357

Open
1 of 7 tasks
itscarlo-nobnos opened this issue Jan 10, 2024 · 0 comments
Open
1 of 7 tasks

Comments

@itscarlo-nobnos
Copy link

Issue Report

Issue Description

crypto_hist.set_index("time") raises KeyError(f"None of {missing} are in the columns")

This statement is not explained on the Merge Data from BTC, LTC and ETC section from Portfolio #3, of the Financial Analysis workshop documentation.

Where is the relevant portion of the documentation located? Line 340 from the Financial Analysis workshop file, Portfolio #3. The code, crypto_hist.set_index("time") in the Merge Data from BTC, LTC and ETC section.

crypto_hist.set_index("time")

What would you suggest it be replaced with? Suggest that this line be removed. If you run the crypto_hist statement in the interactive console, the output already shows the 'time' column indexed.

I ran the code without the crypto_hist.set_index("time") statement on line 340 and the file generated the necessary plots and values.

Other information

  • Is the problem specific to documentation for a particular version of Spyder?

    • N/A
    • Spyder 5 (master)
    • Spyder 4 (4.x)
    • Spyder 3 (3.x, frozen)
  • Are you planning on submitting a Github pull request with a suitable change?

    • Yes
    • No
    • Maybe so

I was going to, but after reading the contributing guidelines, my interpretation was to submit as an issue since the documentation for the workshop stated that it doesn't really explain the procedures on the code. Perhaps removing this line of code, may be enough to avoid further inquiry or confusion for workshop participants, without generating a pull request? I would be happy to submit one if someone from the team let's me know that it is the approach we should take.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant