I'm writing python-binding for project A.
My python-binding depends on the compile output of project A(It is a .so
file), and the project A is not installed in the system(so we can't find
the .so files in the system libraries pathes)
What's the elegant way to package my python-binding, so that I can install
everything by run `python setup.py` ?
Any suggestions and comments will be appreciated :)
I'm trying to write a script to get information about a source
distributions requirements (from the source distribution), but I'm not
sure how to access the tests_require and setup_requires that can
sometimes be found in the setup.py?
Apologies if this is really simple, and I've just missed the answer, but
I've searched for it a few times now, and not come up with anything.
When I brought up enabling Markdown previously, I was a bit over-eager and
started talking implementation before there was any sort of consensus about
it in principle, so it was a bit of a straw-man.
The previous discussion seemed to rest with the onus being on the user to
do it themselves, perhaps by installing (the non-Python) pandoc
(non-trivial on Windows) as well as pypandoc and then integrating it into
twine or some such.
There seems to be a chasm between the GitHubbers that have various issues
and PRs to this effect on the pypa/readme_renderer repo that are met with a
frustrating silence from people with commit-power. Is the solution to
basically write a full spec (PEP?) before touching any code? That seems
like an actionable solution, but is it simply going to be rejected
out-of-hand because of the "just learn rST" sentiment among the maintainers?
Metadata 2.0 has been deferred-in-practice for quite some time, but I
just updated the PEP itself to reflect the deferral and link to more
of the incremental improvement PEPs:
This makes the current policy that enhancement proposals should avoid
depending on the definition and implementation of metadata 2.0
P.S. PEP 459 (standard metadata extensions) depends on 426, and has
also been marked as Deferred
Nick Coghlan | ncoghlan(a)gmail.com | Brisbane, Australia
I am trying to upload a new package to PyPi with this command:
$ python3 setup.py sdist upload
The process seems to go on well until the running upload bit, at which point I get this exception:
Traceback (most recent call last):
File "setup.py", line 33, in <module>
"Topic :: Scientific/Engineering :: GIS",
File "/usr/lib/python3.4/distutils/core.py", line 148, in setup
File "/usr/lib/python3.4/distutils/dist.py", line 955, in run_commands
File "/usr/lib/python3.4/distutils/dist.py", line 974, in run_command
File "/usr/lib/python3.4/distutils/command/upload.py", line 65, in run
self.upload_file(command, pyversion, filename)
File "/usr/lib/python3.4/distutils/command/upload.py", line 139, in upload_file
user_pass = (self.username + ":" + self.password).encode('ascii')
TypeError: Can't convert 'NoneType' object to str implicitly
I verified that Topic :: Scientific/Engineering :: GIS is a valid topic. What else am I missing?
Sent from [ProtonMail](https://protonmail.ch), encrypted email based in Switzerland.