Lambda problems in summarizer process
See original GitHub issueHi,
I’m currently using Pandas-profiling to get information from a parquet file. My dataframe contains 140 columns.
When I try to generate the profiling report, I’m getting this error:
TypeError: <lambda>() argument after * must be an iterable, not bool
I tried to change the column position but the error persists.
My Code is:
df = pd.read_parquet("ConsultationForm.parquet", columns= sorted(columnNames),engine="pyarrow")
df = df.fillna(value=np.nan)
df.head()
profile = ProfileReport(df, title="Pandas Profiling Report", explorative=True, minimal=True)
profile.to_file('ConsultationForm_profiling3.html')
I’m doing something wrong?
Thanks
Issue Analytics
- State:
- Created 3 years ago
- Comments:7
Top Results From Across the Web
What's in a Lambda?. An overview of anonymous functions in…
Using lambda functions solves this problem: the programmer can define a lambda function and use it immediately without breaking the flow of the...
Read more >Lambda Function in Python - How and When to use?
While normal functions are defined using the def keyword, anonymous functions are defined using the lambda keyword.
Read more >Lambda function scaling - AWS Documentation
To summarize, your function's concurrency is the number of concurrent requests that it's handling at the same time. In response to an increase...
Read more >13 AWS Lambda design considerations you need to know about
If you're designing with AWS Lambda, here are a few things you'll need to keep ... Breaking the problem into smaller, more manageable...
Read more >AWS Lambda - does it fit in with data processing
In this post, I will summarize the good and bad sides of my recent experiences with AWS Lambda applied to the data processing....
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Good catch, it’s a special case when one or more columns are fully empty. Until I’ve patched it, you can use this workaround (dropping empty columns):
@Jrecos I’ve just released v2.10.1 that should resolve your issue!
Want me to continue to support this package? Please consider sponsoring