From 8b5d4708a02be803f8d0aa2b1ae1560e141998cd Mon Sep 17 00:00:00 2001
From: "Michael J. Sullivan" <sully@msully.net>
Date: Tue, 31 Jul 2018 15:51:14 -0700
Subject: [PATCH] Change a use of frozenset[int] to FrozenSet[int] (#2352)

Using FrozenSet is I think preferred (because it works in general) and
I am about to propose a mypy PR that breaks this particular use.
---
 third_party/2and3/pymysql/__init__.pyi | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/third_party/2and3/pymysql/__init__.pyi b/third_party/2and3/pymysql/__init__.pyi
index 2fd642c27..523c6014b 100644
--- a/third_party/2and3/pymysql/__init__.pyi
+++ b/third_party/2and3/pymysql/__init__.pyi
@@ -1,5 +1,5 @@
 import sys
-from typing import Union, Tuple, Callable
+from typing import Union, Tuple, Callable, FrozenSet
 
 from .connections import Connection as _Connection
 from .constants import FIELD_TYPE as FIELD_TYPE
@@ -30,7 +30,7 @@ threadsafety: int
 apilevel: str
 paramstyle: str
 
-class DBAPISet(frozenset[int]):
+class DBAPISet(FrozenSet[int]):
     def __ne__(self, other) -> bool: ...
     def __eq__(self, other) -> bool: ...
     def __hash__(self) -> int: ...