From 27b75652e060cb1574e130c5ab4e2a468777475e Mon Sep 17 00:00:00 2001
From: Michael Puehringer <michael.puehringer@datavisyn.io>
Date: Tue, 5 Apr 2022 14:21:13 +0200
Subject: [PATCH] Added MANIFEST.in file

---
 MANIFEST.in |  1 +
 setup.py    | 11 ++++-------
 2 files changed, 5 insertions(+), 7 deletions(-)
 create mode 100644 MANIFEST.in

diff --git a/MANIFEST.in b/MANIFEST.in
new file mode 100644
index 000000000..538ee1be9
--- /dev/null
+++ b/MANIFEST.in
@@ -0,0 +1 @@
+recursive-include tdp_core *
diff --git a/setup.py b/setup.py
index eae4018a9..e2c385f10 100644
--- a/setup.py
+++ b/setup.py
@@ -45,7 +45,7 @@ def requirements(file):
     'Programming Language :: Python :: 3.10'
   ],
 
-  python_requires='>=3',
+  python_requires='>=3.10',
 
   # You can just specify the packages manually here if your project is
   # simple. Or you can use find_packages().
@@ -60,12 +60,9 @@ def requirements(file):
     'develop': requirements('requirements_dev.txt'),
   },
 
-  # If there are data files included in your packages that need to be
-  # installed, specify them here.  If using Python 2.6 or less, then these
-  # have to be included in MANIFEST.in as well.
-  package_data={
-    pkg['name']: ['*/**/*']
-  },
+  # Include all files from the MANIFEST.in file.
+  include_package_data=True,
+  package_data={},
 
   # Although 'package_data' is the preferred approach, in some case you may
   # need to place data files outside of your packages. See: