Skip to content

Commit 43e0beb

Browse files
committed
Modifiche al file setup.py
1 parent 0f9ba3c commit 43e0beb

File tree

4 files changed

+23
-45
lines changed

4 files changed

+23
-45
lines changed

Diff for: .idea/.name

-1
This file was deleted.

Diff for: .idea/MSX Tape Tools.iml

-17
This file was deleted.

Diff for: .idea/modules.xml

+1-1
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

Diff for: setup.py

+22-26
Original file line numberDiff line numberDiff line change
@@ -73,15 +73,15 @@
7373
#
7474
# This field corresponds to the "Home-Page" metadata field:
7575
# https://packaging.python.org/specifications/core-metadata/#home-page-optional
76-
url='https://github.com/pypa/sampleproject', # Optional
76+
url='https://github.com/fmaida/msxtools', # Optional
7777

7878
# This should be your name or the name of the organization which owns the
7979
# project.
80-
author='The Python Packaging Authority', # Optional
80+
author='Francesco Maida', # Optional
8181

8282
# This should be a valid email address corresponding to the author listed
8383
# above.
84-
author_email='pypa-dev@googlegroups.com', # Optional
84+
author_email='francesco.maida@gmail.com', # Optional
8585

8686
# Classifiers help users find your project by categorizing it.
8787
#
@@ -96,15 +96,13 @@
9696

9797
# Indicate who your project is intended for
9898
'Intended Audience :: Developers',
99-
'Topic :: Software Development :: Build Tools',
99+
'Topic :: Software Development :: Utilities',
100100

101101
# Pick your license as you wish
102102
'License :: OSI Approved :: MIT License',
103103

104104
# Specify the Python versions you support here. In particular, ensure
105105
# that you indicate whether you support Python 2, Python 3 or both.
106-
'Programming Language :: Python :: 2',
107-
'Programming Language :: Python :: 2.7',
108106
'Programming Language :: Python :: 3',
109107
'Programming Language :: Python :: 3.4',
110108
'Programming Language :: Python :: 3.5',
@@ -115,7 +113,7 @@
115113
# project page. What does your project relate to?
116114
#
117115
# Note that this is a string of words separated by whitespace, not a list.
118-
keywords='sample setuptools development', # Optional
116+
keywords='msx cas tape audio', # Optional
119117

120118
# You can just specify package directories manually here if your project is
121119
# simple. Or you can use find_packages().
@@ -134,7 +132,7 @@
134132
#
135133
# For an analysis of "install_requires" vs pip's requirements files see:
136134
# https://packaging.python.org/en/latest/requirements.html
137-
install_requires=['peppercorn'], # Optional
135+
# install_requires=['peppercorn'], # Optional
138136

139137
# List additional groups of dependencies here (e.g. development
140138
# dependencies). Users will be able to install these using the "extras"
@@ -144,26 +142,26 @@
144142
#
145143
# Similar to `install_requires` above, these must be valid existing
146144
# projects.
147-
extras_require={ # Optional
148-
'dev': ['check-manifest'],
149-
'test': ['coverage'],
150-
},
145+
# extras_require={ # Optional
146+
# 'dev': ['check-manifest'],
147+
# 'test': ['coverage'],
148+
# },
151149

152150
# If there are data files included in your packages that need to be
153151
# installed, specify them here.
154152
#
155153
# If using Python 2.6 or earlier, then these have to be included in
156154
# MANIFEST.in as well.
157-
package_data={ # Optional
158-
'sample': ['package_data.dat'],
159-
},
155+
# package_data={ # Optional
156+
# 'sample': ['package_data.dat'],
157+
# },
160158

161159
# Although 'package_data' is the preferred approach, in some case you may
162160
# need to place data files outside of your packages. See:
163161
# http://docs.python.org/3.4/distutils/setupscript.html#installing-additional-files
164162
#
165163
# In this case, 'data_file' will be installed into '<sys.prefix>/my_data'
166-
data_files=[('my_data', ['data/data_file'])], # Optional
164+
# data_files=[('my_data', ['data/data_file'])], # Optional
167165

168166
# To provide executable scripts, use entry points in preference to the
169167
# "scripts" keyword. Entry points provide cross-platform support and allow
@@ -172,11 +170,11 @@
172170
#
173171
# For example, the following would provide a command called `sample` which
174172
# executes the function `main` from this package when invoked:
175-
entry_points={ # Optional
176-
'console_scripts': [
177-
'sample=sample:main',
178-
],
179-
},
173+
# entry_points={ # Optional
174+
# 'console_scripts': [
175+
# 'sample=sample:main',
176+
# ],
177+
# },
180178

181179
# List additional URLs that are relevant to your project as a dict.
182180
#
@@ -188,9 +186,7 @@
188186
# maintainers, and where to support the project financially. The key is
189187
# what's used to render the link text on PyPI.
190188
project_urls={ # Optional
191-
'Bug Reports': 'https://github.com/pypa/sampleproject/issues',
192-
'Funding': 'https://donate.pypi.org',
193-
'Say Thanks!': 'http://saythanks.io/to/example',
194-
'Source': 'https://github.com/pypa/sampleproject/',
189+
'Bug Reports': 'https://github.com/fmaida/msxtools/issues',
190+
'Source': 'https://github.com/fmaida/msxtools',
195191
},
196-
)
192+
)

0 commit comments

Comments
 (0)