mirror of
https://github.com/AJaySi/ALwrity.git
synced 2026-04-25 08:55:58 +03:00
[GH-ISSUE #157] Issue: NumPy Import Error in pandas_ta Library #452
Labels
No labels
AI Content Agents
AI Content Strategy
AI Content planning
AI Marketing Tools
AI SEO
AI personalization
AI writer
ALwrity Copi-lot
Alwrity web search
Anthropic
DeepSeek
Gemini AI
Integration
LLM
OnBoarding
OnBoarding
RAG knowledgebase Memory
bug
documentation
enhancement
good first issue
help wanted
invalid
openai
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/ALwrity#452
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @cypheroxide on GitHub (Mar 4, 2025).
Original GitHub issue: https://github.com/AJaySi/ALwrity/issues/157
Originally assigned to: @AJaySi, @cypheroxide, @uniqueumesh on GitHub.
Issue: NumPy Import Error in pandas_ta Library
Summary
After successfully resolving the dependencies installation issues, I encountered an error when trying to run the application due to a NumPy import issue in the pandas_ta library.
Environment
Error Description
When running the application with
streamlit run alwrity.py, the following error occurs:Error Traceback
Root Cause
In recent versions of NumPy, the
NaNconstant is namednan(lowercase) instead ofNaN(uppercase). The pandas_ta library is trying to import the uppercase version, which no longer exists.Reproduction Steps
streamlit run alwrity.pySolution
Edit the following file in your virtual environment:
Change line 2 from:
To:
After making this change, the application runs successfully without any further errors.
Proposed Long-Term Solutions
I've confirmed this solution works on my system (Windows 11, Python 3.12.9). Let me know if there are any questions or if you need additional information.
@AJaySi commented on GitHub (Mar 4, 2025):
This is useful. Thank you.
Strange that these errors are not present in my environment(not a vanilla system).
@uniqueumesh too confirmed in a new virtual environment and installation went without problems.
Looking forward to include your changes soon. Thank you.
I have posted few questions for you in our other thread.
Regards.
@AJaySi commented on GitHub (Mar 13, 2025):
@cypheroxide Fixed these in his latest patch. Closing this.