Merge pull request #76 from treasure-data/v120

Prepare for v1.2.0 release
treasure-data · Mar 18, 2020 · 8d9a79f · 8d9a79f
2 parents 08f6a75 + 4d299f7
commit 8d9a79f
Show file tree

Hide file tree

Showing 3 changed files with 7 additions and 12 deletions.
diff --git a/CHANGELOG.rst b/CHANGELOG.rst
@@ -1,6 +1,12 @@
 Changelog
 =========
 
+v1.2.0 (2020-03-18)
+-------------------
+
+- Support nullable column containing ``pandas.NA``, which was `newly introduced in pandas 1.0.0 <https://pandas.pydata.org/pandas-docs/version/1.0.0/whatsnew/v1.0.0.html#experimental-na-scalar-to-denote-missing-values>`__. The ``Writer`` module internally converts ``pandas.NA`` into ``None`` before ingesting ``pandas.DataFrame`` to Treasure Data. Note that ``Writer#write_dataframe`` may behave differently between before and after upgrading pandas to 1.0.0 because of the experimental, backward-incompatible updates on the dependent package. (`#72 <https://github.com/treasure-data/pytd/pull/72>`__)
+
+
 v1.1.0 (2020-03-07)
 -------------------
 

diff --git a/pytd/version.py b/pytd/version.py
@@ -1 +1 @@
-__version__ = "1.1.0"
+__version__ = "1.2.0"
diff --git a/pytd/writer.py b/pytd/writer.py
@@ -17,17 +17,6 @@
 
 logger = logging.getLogger(__name__)
 
-if pd.__version__ >= "1.0.0":
-    logger.warning(
-        "You are using pandas 1.0.0 or later, but pytd is not fully tested on "
-        "the major version. Since the version has introduced some "
-        "experimental, backward-incompatible features, there might be a "
-        "chance of unexpected runtime failure when you handle a DataFrame "
-        "containing null or array. See pandas official documentation for more "
-        "information: "
-        "https://pandas.pydata.org/pandas-docs/version/1.0.0/whatsnew/v1.0.0.html"
-    )
-
 
 def _is_pd_na(x):
     is_na = pd.isna(x)