How to write a __repr__ when one of the inputs is a dataframe?

By -

I have a class that takes a pandas dataframe as one of parameters. I've not been very good at adding __repr__ to my code so now I'm trying to go back and add to all the existing codebase. But here I run into the issue:

import pandas as pd

class Foo:
    def __init__(self, data: pd.DataFrame, some_val: str):
        self.data = data
        self.some_val = val

    def __repr__(self):
        return f'Foo(data={self.data}, some_val={self.some_val})'

So in this example if I call repr() on an instance of my class I will get something like:

Out[7]: 'Foo(data=       xcentre   ycentre  ...
n99996     99996  316065.0  295205.0  ...  undef -99.0 
      undef\n99997     99997  316075.0  295205.0  ...  undef -99.0
       undef\n99998     99998  316065.0  295215.0  ...  undef -99.0 
      undef\n99999     99999  316075.0  295215.0  ...  undef -99.0
       undef\n\n[100000 rows x 121 columns], some_val='blabla')'

It is also no surprise I get syntax errors when I try to run eval() on it.

So how should I correctly use __repr__ in this case?



from Recent Questions - Stack Overflow https://ift.tt/3dkEaDg
https://ift.tt/eA8V8J

Comments

Post a Comment

Popular posts from this blog

Today Walkin 14th-Sept

By -
Image
14th Sept 2017 ( GO Through all List) Read Walkin details properly , Try to call company before attending if possible !!! ==================================== 1. Myntra through fresherworld (Call Based , Venue shared to shortlisted candidates) _____________________________ 2. Magna : Hiring for Client Harman : C++
Read more

Hibernate Search - Elasticsearch with JSON manipulation

By -
Elasticsearch with JSON manipulation Elasticsearch ships with many features. It is possible that at some point, one feature you need will not be exposed by the Search DSL. To work around such limitations, Hibernate Search provides ways to: Transform the HTTP request sent to Elasticsearch for search queries. Read the raw JSON of the HTTP response received from Elasticsearch for search queries. Direct changes to the HTTP request may conflict with Hibernate Search features and be supported differently by different versions of Elasticsearch. Similarly, the content of the HTTP response may change depending on the version of Elasticsearch, depending on which Hibernate Search features are used, and even depending on how Hibernate Search features are implemented. Thus, features relying on direct access to HTTP requests or responses cannot be guaranteed to continue to work when upgrading Hibernate Search, even for micro upgrades (x.y.z to x.y.(z+1)). Use this at your own risk.
Read more

Spring Elasticsearch Operations

By -
Elasticsearch Operations Spring Data Elasticsearch uses two interfaces to define the operations that can be called against an Elasticsearch index. These are ElasticsearchOperations and ReactiveElasticsearchOperations. Whereas the first is used with the classic synchronous implementations, the second one uses reactive infrastructure. The default implementations of the interfaces offer: Read/Write mapping support for domain types. A rich query and criteria api. Resource management and Exception translation. ElasticsearchTemplate The ElasticsearchTemplate is an implementation of the ElasticsearchOperations interface using the Transport Client. @Configuration public class TransportClientConfig extends ElasticsearchConfigurationSupport {   @Bean   public Client elasticsearchClient() throws UnknownHostException {                      Settings settings = Settings.builder().put("cluster.name", "elasticsearch").build();     TransportClient client = new P
Read more