Add User-Agent

[sheaur]

No description provided.

[Copilot]

Pull request overview

Adds an explicit HTTP User-Agent header when fetching Meteoclimatic station RSS feeds.

Changes:

• Switches urlopen(url) to urlopen(Request(...)) to include a User-Agent header.
• Minor formatting adjustments around the raised MeteoclimaticError.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

The hard-coded User-Agent value references "HomeAssistant", but this library is published as "pymeteoclimatic" and is not Home Assistant-specific (see README.md / setup.py). Consider using a library-identifying UA string (e.g., package name + version) and/or making the User-Agent configurable via the client constructor so downstream consumers can set their own UA.

Suggested change

	def weather_at_station(self, station_code):
	url = self._base_url.format(station_code=station_code)
	req = Request(url, headers={"User-Agent": "HomeAssistant Meteoclimatic"})
	def __init__(self, user_agent: str | None = None) -> None:
	"""Initialize the Meteoclimatic client.
	Args:
	user_agent: Optional User-Agent string to use for HTTP requests.
	If not provided, a default identifying this library is used.
	"""
	self._user_agent = user_agent or "pymeteoclimatic"
	def weather_at_station(self, station_code):
	url = self._base_url.format(station_code=station_code)
	req = Request(url, headers={"User-Agent": self._user_agent})

[adrianmo]

Agree with this comment. Even though this library is used in Home Assistant's Meteoclimatic integration, it can also be used on its own or from any other platform.

It'd use pymeteoclimatic/<version>.

[adrianmo]

Thanks for the PR. Can we also add/update test cases to make sure the changes are covered? Thanks

[sheaur]

I've tried to test it, but being in the core I haven't had much time.

[sheaur]

The problem, in principle, is that Meteoclimatic has blocked access.