Q.(a) List any two characteristics of Pandas library in Python.

Series vs Data Structures — A First Look

Imagine you walk into a library. You see books arranged on shelves. That arrangement — the shelves, the order, the categories — is a data structure. It is a way of organising information so you can find it, add to it, or remove it without chaos. Now imagine you pick up a single book from that shelf. That book has a title, an author, and a year of publication. That single, self-contained record is like a series — one item, with its own internal order and meaning.

In the world of information management, these two ideas are foundational. A data structure is the container, the system, the framework. A series is one coherent unit of content inside that framework. You cannot have a meaningful series without a data structure to hold it, and a data structure without series would be an empty shelf.

The Intuition: A Filing Cabinet

Think of a filing cabinet in an office. The cabinet itself, with its drawers and labelled dividers, is a data structure. It tells you where things go, how they are grouped, and how to retrieve them. Inside one drawer, you might have a folder labelled "Quarterly Reports 2024." That folder is a series — a set of related documents that belong together, arranged in a logical order (say, by month). The series has a beginning and an end; it is a complete unit of information.

Now, if you pull out that folder and look inside, you see individual reports. Each report is a record or an item. The series is the collection of those items, bound by a common theme and a consistent structure. The data structure is the cabinet that keeps the series safe and findable.

The Precise Meaning

In formal terms, a data structure is a specialised format for organising, processing, retrieving, and storing data. It defines the relationships between data elements and the operations that can be performed on them. Examples include arrays, linked lists, stacks, queues, trees, and graphs. Each has its own rules about how data is added, removed, or accessed.

A series (in the context of data management) is a sequence of related data points or records that share a common schema or purpose. It is often time-ordered or logically ordered. In a database, a series might be a table of monthly sales figures. In a library catalogue, it might be a set of books published under the same title across different years.

Why It Matters

For a commerce or humanities student, this distinction is not just technical jargon. It affects how you think about information in the real world.

• In business, a company's customer database is a data structure. Each customer's purchase history is a series. If the data structure is poorly designed, you cannot find the series you need. If the series is incomplete, you cannot analyse customer behaviour.
• In history, an archive of letters is a data structure. The letters from a particular decade form a series. The structure determines whether you can trace a narrative across time. …

DataFrame Querying: Finding What You Need in a Table

Think of a DataFrame as a digital spreadsheet — rows of records (like each customer, each student, each transaction) and columns of attributes (name, age, city, purchase amount). Querying is simply the act of asking questions of that table: "Show me only the rows where the city is Delhi" or "Give me all students who scored above 80 in Economics."

You already do this in everyday life. When you open your contacts app and type "R" to see only names starting with R, you are querying. When you filter your email to show only unread messages, you are querying. A DataFrame query is the same idea, but more powerful and precise.

The Precise Meaning

In the context of a DataFrame (a two-dimensional, labelled data structure), querying means selecting a subset of rows and/or columns based on some condition or set of conditions. The original DataFrame remains unchanged; you get a new, smaller view of the data that answers your specific question.

The key parts of any query are:

• Which rows? You specify a condition — for example, rows where age > 18 or city == "Mumbai".
• Which columns? You specify which attributes you want to see — for example, only name and score, or all columns.

A query can combine multiple conditions using logical operators like AND, OR, and NOT. For instance: "Show me all rows where the city is Bangalore AND the purchase amount is greater than 5000."

Why It Matters

DataFrame querying is the foundation of data analysis. Without it, you are stuck looking at the entire table — thousands or millions of rows — and trying to spot patterns by eye. That is impossible for any real-world dataset.

Querying lets you:

• Find specific records — "Which customers have not paid their bill?"
• Compare groups — "How do sales in the North zone differ from the South zone?"
• Prepare data for further analysis — "Extract only the records from the last financial year."
• Check for errors — "Are there any rows where the age is negative?"

A Simple Example in Words

Imagine a DataFrame called Students with columns: Name, Stream, Percentage, City.

A query like "Show me all Commerce students" would return a new table containing only those rows where the Stream column has the value "Commerce". All columns — Name, Stream, Percentage, City — would still appear, but only for Commerce students.

A more specific query: "Show me the names and percentages of Commerce students from Delhi who scored above 75." This query:

1. Filters rows to those where Stream is "Commerce" AND City is "Delhi" AND Percentage is greater than 75.
2. Selects only the Name and Percentage columns.

The result is a small, focused table — exactly the information you need, nothing more. …