@ssteinbach I’m pretty sure tests_require has been around a very long time. I’m less sure about
project_urls. You can refer to the history, which may or may not make mention of that particular change.
Hi all, I'm updating some of my packages to use the declarative setup.cfg way of specifying package options instead of listing them in setup.py. But I was just curious as to what the plan is for future in terms of setup.cfg vs pyproject.toml - is the long term plan to have everything declared in pyproject.toml instead of setup.cfg?
@jaraco Thanks! We're dealing with really old versions of setuptools. We ended up doing a kind of ugly thing in setup.py to detect and error out: PixarAnimationStudios/OpenTimelineIO#397
Basically I want to parse and interpret the content of the
python_requires configuration item, and that seems to be parseable by SpecifierSet
an alternative would be to do something like
Requirement.parse('python' + python_requires).specifiers
Seems like I can do it if I make them data files, but then the shebang has to be hard-coded.
Anyone know if there's a way to do that with console_scripts?
whats the actual use-case
It's not a terribly uncommon use case to put scripts in libexec or another place on the path with lower or higher precedence than bin.
It might be that they don't care about portability (as in, what the shebang does in a virtualenv) in this case, but we do allow specifying the target directory for other things, and it kinda sucks to say, "Oh this just won't work in a virtualenv"
Plus there is the
--script-dir argument, which I gather allows you to, at runtime, specify a target for all scripts.
whats the context of the script? something like a git addon?
thats not part of the toolchain that does wheels and puts them in place
so you either add a own installer, or prevent wheels
I'd like to be able to recommend what to do if they want something that does whatever console_scripts / scripts does, but installs to a different location than bin/
Hi there, does someone know I can get the list of user-requested
I need to know what a user selected in order to accordingly set a CMake option: pypa/setuptools#1712
extras inside my setup.py?I need to know what a user selected in order to accordingly set a CMake option: pypa/setuptools#1712
@ax3l That’s not possible as far as I know. If the current project depends on it to decide how to build itself, then it’s not really an extra (as intended). Extras are intended for install-time dependency resolution, not build-time. You’ll want to structure your project so it can support running with and without the extras at run-time… maybe that means building with and without the libs the extras might require, or maybe it means pushing that functionality into the extras themselves.
nvm. I see the conversation is happening in Github.
@jaraco @benoit-pierre Any objections?
Anything you want to see merged before the release?
(I don't have an enormous amount of time for this, so anything that requires too much work is equivalent to just delaying the release)
Hello. I'm experiencing a problem where the end symptom is setuptools complaining setuptools-scm was unable to detect version for.... Ultimately this is during a conda environment create, via pip as an intermediary. I can reproduce it with pip directly just attempting to install one package. The package in question is being installed from a github repo via SSH. It is not in the root of the repo. The setup.py looks like this:
import os
from setuptools import setup
setup(
name = 'c12e_data',
packages = ['c12e.data'],
use_scm_version = {
'root' : '..',
'relative_to': os.path.dirname(__file__)
},
install_requires = [
'typing_extensions'
],
tests_require = [
'hypothesis',
'pytest >= 3.8.1, < 4.0',
'c12e_testing'
],
extras_require = {
's3': ['boto3 >= 1.0.0, < 2.0.0']
},
setup_requires = [
'setuptools_scm',
'pytest-runner'
]
)This is in the c12e_data directory within the git repo root. The conda environment.yml pins the versions of pip and setuptools according to:
channels:
- conda-forge
- pytorch
- defaults
dependencies:
- pip=19.0.1
- python=3.6.8
- setuptools=40.7.3
- toolz=0.9.0
- scikit-learn
- pip:
- git+ssh://git@github.com/CognitiveScale/c12e-python.git@v1.0.4#subdirectory=c12e_dataThe really odd thing is that this exact install was working fine a few weeks ago, and so far as I can tell nothing has changed (the git tag specified is old and unchanged, the versions of pip and setuptools are pinned and unchanged). All I can think of is that some unpinned transitive dependency (of setuptools or something) must have changed.
I have spent several hours following various issue threads and checking with respect to them (including detailed debug output from
pip and setuptools but not gotten anywhere. Has anyone seen anything similar recently?
Setuptools has no dependencies.