Skip to content

Commit d706265

Browse files
committed
Updated with Copyright and License info
1 parent 9625c75 commit d706265

5 files changed

Lines changed: 4 additions & 209 deletions

File tree

-17.8 KB
Binary file not shown.
18.8 KB
Binary file not shown.

dist/kepconfig-1.0b2.1.tar.gz

13.7 KB
Binary file not shown.

dist/kepconfig-1.0b2.tar.gz

-16.3 KB
Binary file not shown.

setup.py

Lines changed: 4 additions & 209 deletions
Original file line numberDiff line numberDiff line change
@@ -11,9 +11,9 @@
1111

1212
setuptools.setup(
1313
name="kepconfig",
14-
version="1.0b2",
15-
author="Ray Labbe",
16-
author_email="author@example.com",
14+
version="1.0b2.1",
15+
author="PTC Inc",
16+
author_email="presales.support@kepware.com",
1717
description="API package for Kepware Configuration API",
1818
keywords="Kepware OPC Configuration Thingworx",
1919
long_description=long_description,
@@ -23,215 +23,10 @@
2323
packages=setuptools.find_packages(),
2424
classifiers=[
2525
"Development Status :: 4 - Beta",
26+
'License :: OSI Approved :: MIT License',
2627
"Programming Language :: Python :: 3",
2728
"Operating System :: OS Independent",
2829
"Intended Audience :: Manufacturing",
2930
],
3031
python_requires='>=3.6',
3132
)
32-
# """A setuptools based setup module.
33-
# See:
34-
# https://packaging.python.org/guides/distributing-packages-using-setuptools/
35-
# https://github.com/pypa/sampleproject
36-
# """
37-
38-
# # Always prefer setuptools over distutils
39-
# from setuptools import setup, find_packages
40-
# from os import path
41-
# # io.open is needed for projects that support Python 2.7
42-
# # It ensures open() defaults to text mode with universal newlines,
43-
# # and accepts an argument to specify the text encoding
44-
# # Python 3 only projects can skip this import
45-
# from io import open
46-
47-
# here = path.abspath(path.dirname(__file__))
48-
49-
# # Get the long description from the README file
50-
# with open(path.join(here, 'README.md'), encoding='utf-8') as f:
51-
# long_description = f.read()
52-
53-
# # Arguments marked as "Required" below must be included for upload to PyPI.
54-
# # Fields marked as "Optional" may be commented out.
55-
56-
# setup(
57-
# # This is the name of your project. The first time you publish this
58-
# # package, this name will be registered for you. It will determine how
59-
# # users can install this project, e.g.:
60-
# #
61-
# # $ pip install sampleproject
62-
# #
63-
# # And where it will live on PyPI: https://pypi.org/project/sampleproject/
64-
# #
65-
# # There are some restrictions on what makes a valid project name
66-
# # specification here:
67-
# # https://packaging.python.org/specifications/core-metadata/#name
68-
# name='sampleproject', # Required
69-
70-
# # Versions should comply with PEP 440:
71-
# # https://www.python.org/dev/peps/pep-0440/
72-
# #
73-
# # For a discussion on single-sourcing the version across setup.py and the
74-
# # project code, see
75-
# # https://packaging.python.org/en/latest/single_source_version.html
76-
# version='1.3.0', # Required
77-
78-
# # This is a one-line description or tagline of what your project does. This
79-
# # corresponds to the "Summary" metadata field:
80-
# # https://packaging.python.org/specifications/core-metadata/#summary
81-
# description='A sample Python project', # Optional
82-
83-
# # This is an optional longer description of your project that represents
84-
# # the body of text which users will see when they visit PyPI.
85-
# #
86-
# # Often, this is the same as your README, so you can just read it in from
87-
# # that file directly (as we have already done above)
88-
# #
89-
# # This field corresponds to the "Description" metadata field:
90-
# # https://packaging.python.org/specifications/core-metadata/#description-optional
91-
# long_description=long_description, # Optional
92-
93-
# # Denotes that our long_description is in Markdown; valid values are
94-
# # text/plain, text/x-rst, and text/markdown
95-
# #
96-
# # Optional if long_description is written in reStructuredText (rst) but
97-
# # required for plain-text or Markdown; if unspecified, "applications should
98-
# # attempt to render [the long_description] as text/x-rst; charset=UTF-8 and
99-
# # fall back to text/plain if it is not valid rst" (see link below)
100-
# #
101-
# # This field corresponds to the "Description-Content-Type" metadata field:
102-
# # https://packaging.python.org/specifications/core-metadata/#description-content-type-optional
103-
# long_description_content_type='text/markdown', # Optional (see note above)
104-
105-
# # This should be a valid link to your project's main homepage.
106-
# #
107-
# # This field corresponds to the "Home-Page" metadata field:
108-
# # https://packaging.python.org/specifications/core-metadata/#home-page-optional
109-
# url='https://github.com/pypa/sampleproject', # Optional
110-
111-
# # This should be your name or the name of the organization which owns the
112-
# # project.
113-
# author='The Python Packaging Authority', # Optional
114-
115-
# # This should be a valid email address corresponding to the author listed
116-
# # above.
117-
# author_email='pypa-dev@googlegroups.com', # Optional
118-
119-
# # Classifiers help users find your project by categorizing it.
120-
# #
121-
# # For a list of valid classifiers, see https://pypi.org/classifiers/
122-
# classifiers=[ # Optional
123-
# # How mature is this project? Common values are
124-
# # 3 - Alpha
125-
# # 4 - Beta
126-
# # 5 - Production/Stable
127-
# 'Development Status :: 3 - Alpha',
128-
129-
# # Indicate who your project is intended for
130-
# 'Intended Audience :: Developers',
131-
# 'Topic :: Software Development :: Build Tools',
132-
133-
# # Pick your license as you wish
134-
# 'License :: OSI Approved :: MIT License',
135-
136-
# # Specify the Python versions you support here. In particular, ensure
137-
# # that you indicate whether you support Python 2, Python 3 or both.
138-
# # These classifiers are *not* checked by 'pip install'. See instead
139-
# # 'python_requires' below.
140-
# 'Programming Language :: Python :: 2',
141-
# 'Programming Language :: Python :: 2.7',
142-
# 'Programming Language :: Python :: 3',
143-
# 'Programming Language :: Python :: 3.5',
144-
# 'Programming Language :: Python :: 3.6',
145-
# 'Programming Language :: Python :: 3.7',
146-
# ],
147-
148-
# # This field adds keywords for your project which will appear on the
149-
# # project page. What does your project relate to?
150-
# #
151-
# # Note that this is a string of words separated by whitespace, not a list.
152-
# keywords='sample setuptools development', # Optional
153-
154-
# # You can just specify package directories manually here if your project is
155-
# # simple. Or you can use find_packages().
156-
# #
157-
# # Alternatively, if you just want to distribute a single Python file, use
158-
# # the `py_modules` argument instead as follows, which will expect a file
159-
# # called `my_module.py` to exist:
160-
# #
161-
# # py_modules=["my_module"],
162-
# #
163-
# packages=find_packages(exclude=['contrib', 'docs', 'tests']), # Required
164-
165-
# # Specify which Python versions you support. In contrast to the
166-
# # 'Programming Language' classifiers above, 'pip install' will check this
167-
# # and refuse to install the project if the version does not match. If you
168-
# # do not support Python 2, you can simplify this to '>=3.5' or similar, see
169-
# # https://packaging.python.org/guides/distributing-packages-using-setuptools/#python-requires
170-
# python_requires='>=2.7, !=3.0.*, !=3.1.*, !=3.2.*, !=3.3.*, !=3.4.*, <4',
171-
172-
# # This field lists other packages that your project depends on to run.
173-
# # Any package you put here will be installed by pip when your project is
174-
# # installed, so they must be valid existing projects.
175-
# #
176-
# # For an analysis of "install_requires" vs pip's requirements files see:
177-
# # https://packaging.python.org/en/latest/requirements.html
178-
# install_requires=['peppercorn'], # Optional
179-
180-
# # List additional groups of dependencies here (e.g. development
181-
# # dependencies). Users will be able to install these using the "extras"
182-
# # syntax, for example:
183-
# #
184-
# # $ pip install sampleproject[dev]
185-
# #
186-
# # Similar to `install_requires` above, these must be valid existing
187-
# # projects.
188-
# extras_require={ # Optional
189-
# 'dev': ['check-manifest'],
190-
# 'test': ['coverage'],
191-
# },
192-
193-
# # If there are data files included in your packages that need to be
194-
# # installed, specify them here.
195-
# #
196-
# # If using Python 2.6 or earlier, then these have to be included in
197-
# # MANIFEST.in as well.
198-
# package_data={ # Optional
199-
# 'sample': ['package_data.dat'],
200-
# },
201-
202-
# # Although 'package_data' is the preferred approach, in some case you may
203-
# # need to place data files outside of your packages. See:
204-
# # http://docs.python.org/3.4/distutils/setupscript.html#installing-additional-files
205-
# #
206-
# # In this case, 'data_file' will be installed into '<sys.prefix>/my_data'
207-
# data_files=[('my_data', ['data/data_file'])], # Optional
208-
209-
# # To provide executable scripts, use entry points in preference to the
210-
# # "scripts" keyword. Entry points provide cross-platform support and allow
211-
# # `pip` to create the appropriate form of executable for the target
212-
# # platform.
213-
# #
214-
# # For example, the following would provide a command called `sample` which
215-
# # executes the function `main` from this package when invoked:
216-
# entry_points={ # Optional
217-
# 'console_scripts': [
218-
# 'sample=sample:main',
219-
# ],
220-
# },
221-
222-
# # List additional URLs that are relevant to your project as a dict.
223-
# #
224-
# # This field corresponds to the "Project-URL" metadata fields:
225-
# # https://packaging.python.org/specifications/core-metadata/#project-url-multiple-use
226-
# #
227-
# # Examples listed include a pattern for specifying where the package tracks
228-
# # issues, where the source is hosted, where to say thanks to the package
229-
# # maintainers, and where to support the project financially. The key is
230-
# # what's used to render the link text on PyPI.
231-
# project_urls={ # Optional
232-
# 'Bug Reports': 'https://github.com/pypa/sampleproject/issues',
233-
# 'Funding': 'https://donate.pypi.org',
234-
# 'Say Thanks!': 'http://saythanks.io/to/example',
235-
# 'Source': 'https://github.com/pypa/sampleproject/',
236-
# },
237-
# )

0 commit comments

Comments
 (0)