Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • 04:02

    jaraco on main

    Re-implement yield_lines as a s… (compare)

  • 04:00
    rodrigomologni opened #2915
  • 02:40

    jaraco on distutils-8f2df0bf6

    (compare)

  • 02:40
    jaraco closed #2914
  • 02:40

    jaraco on main

    Incorporate Fedora's distutil p… Expose _prefix_addition as a cl… Update comment for _distutils_s… and 7 more (compare)

  • 02:37
    jaraco opened #2914
  • 02:37

    jaraco on distutils-8f2df0bf6

    Incorporate Fedora's distutil p… Expose _prefix_addition as a cl… Update comment for _distutils_s… and 5 more (compare)

  • Dec 03 21:03
    bblommers commented #2605
  • Dec 03 14:32
    learnereveryday commented #2544
  • Dec 03 08:32
    jaraco commented #2544
  • Dec 03 08:14
    learnereveryday commented #2544
  • Dec 01 16:02
    msuozzo commented #2839
  • Nov 30 17:15
    mivade commented #1724
  • Nov 30 15:36
    anntzer commented #2823
  • Nov 30 13:29
    idgserpro commented #2514
  • Nov 30 02:18
    jaraco commented #2823
  • Nov 29 13:56

    jaraco on main

    Update comment and docstring. (compare)

  • Nov 29 07:53
    kiorky commented #2893
  • Nov 29 07:42
    anntzer commented #2823
  • Nov 29 07:42
    anntzer commented #2823
drocsid
@drocsid
despite adding it to install_requrires
Ian
@ionox0
what does pip show qds-sdk say?
drocsid
@drocsid
pip show qds-sdk
DEPRECATION: Python 2.7 will reach the end of its life on January 1st, 2020. Please upgrade your Python as Python 2.7 won't be maintained after that date. A future version of pip will drop support for Python 2.7.
Name: qds-sdk
Version: 1.12.0
Summary: Python SDK for coding to the Qubole Data Service API
Home-page: https://github.com/qubole/qds-sdk-py
Author: Qubole
Author-email: dev@qubole.com
License: Apache License 2.0
Location: /private/tmp/id-core-test/id-correlation-offline/env/lib/python2.7/site-packages
Requires: requests, boto, inflection, six, urllib3
Required-by: idc-offline
Ian
@ionox0
are you using a virtualenv? if so is your webserver installed within / using that same virtualenv?
(or using conda)?
drocsid
@drocsid
Yeah I'm not sure what I did wrong that time but it does seem to be working on another attempt. Thanks for the help!
Ian
@ionox0
Np!
Thomas Robitaille
@astrofrog
Is there a document somewhere that describes that the plan for Python packaging is to move away from setuptools commands? I've read it in a few comments but I'd like to find a more official place where this is mentioned so that I can use this to convince the developer communities I'm part of to move in that direction.
Paul Ganssle
@pganssle
No.
It's true that you should, and almost certainly there is at least documentation that says not to use specific commands.
Like upload and register for example are deprecated.
Other stuff it's more complicated and I'd rather err on the side of a "soft launch" rather than add more churn and conflicting documentation when we don't know when the replacements are ready yet.
We can probably deprecate install in the documentation and test entirely.
Ronny Pfannschmidt
@RonnyPfannschmidt
is there any way for setuptools to obtain access to the egg/dist-info folder pip makes before copying out a folder from a build?
Paul Ganssle
@pganssle
I think setuptools makes that folder.
Ronny Pfannschmidt
@RonnyPfannschmidt
@pganssle pip uses setuptools to make that folder, but then the next call to setuptools from pip happens somewhere else
@pganssle im wonderring, because i need setuptools_scm to figure the actual version, and pip copies everything away which makes things strange
Paul Ganssle
@pganssle
I dunno, I would only count on whatever PEP 517 says.
It seems like prepare_metadata_for_build_wheel is at least partially designed for this.
Not sure how that translates into setuptools_scm space.
Ronny Pfannschmidt
@RonnyPfannschmidt
same - i have no idea how to get the metadata i need ^^
Thomas Robitaille
@astrofrog
Hi all, is there a way in setuptools to check whether a version number (e.g. 1.3) satisfies a version specifier? (e.g. ~= 0.9, >= 1.0, != 1.3.4.*, < 2.0)
Thomas Robitaille
@astrofrog
I just found https://packaging.pypa.io/en/latest/specifiers/ which answers my question
Damien Stanton
@damienstanton
Hi all, I am building a local package that needs to include a single pre-compiled .so file. I've tried including this in package_data or data_files fields, but it's not working. Additionally, in my wrapper for the C interface, what path is appropriate to pass into the call to cdll.LoadLibrary("mylib.so")? All the documentation I've found has explained how to include, compile, and link C sources directly, but this isn't what I am doing. Any help is much appreciated :pray:
Ghost
@ghost~5d64af83d73408ce4fc952bd
can somebody help me with setup.py and data_files/package_data?
can't figure how to make it export localizations on pip install
Ghost
@ghost~5d64af83d73408ce4fc952bd
yeah they're right, irc's dead these days
Vicente Mataix Ferrándiz
@loumalouomega
hi everyone, I have a question, how can we deal with binaries dependencies?
I mean, for example for linux
for several .so that depend on one main .so
Lets say that that main so we want to be an independent package of the others
Any idea?
I was thinking just to hardcode the changes on the setup.py
and add the dependencies as usual
Jason R. Coombs
@jaraco
Hi @loumalouomega . Setuptools (and much of the Python Packaging infrastructure) doesn’t do much for managing dependencies outside of the Python ecosystem. Tools like pip and setuptools rely on system package managers (and developers) to have satisfied external dependencies (compilers, Python versions, other libraries) before running the tool. In this section of the Python Packaging User’s Guide, there’s some guidance about how a user might rely on something like Conda or Spack or other tools to manage and install some of the more complicated dependencies. Other packages like lxml and Pillow mainly rely on custom build-time routines (or sometimes just instructions) to ensure that build dependencies are present before statically linking libraries.
Some work has been drafted/discussed on declaring “external dependencies”, but to my knowledge none has matured to a useable state.
For now, I would suggest avoiding using setuptools and setup.py to manage these dependencies and would instead build a custom workflow to orchestrate first the preparation of the external dependencies and second the building of the Python package (setup.py or pyproject.toml) that assumes the presence of the external dependencies.
Vicente Mataix Ferrándiz
@loumalouomega
Thank you very much
I was thinking in use poetry to deal with the dependencies
And adapt it to our case
But maybe I would do as youy suggest
Thank you very much
Axel Huebl
@ax3l
Hi! I am generating in a CMake workflow some libraries via pybind11 and install them already successfully. Now I am also generating a binary executable that I want to distribute with my wheel into a PATH location. Just adding the generated binary to setup(..., scripts=['mytool']) does not work (not found) and just generating it in extdir installs it alongside the python prefix ('-DCMAKE_RUNTIME_OUTPUT_DIRECTORY=' + extdir), but does not add it to the PATH. What do you recommend to specify in setuptools:setup to install an executable that is generated from an external build?
This is what I am doing so far for libraries: https://github.com/openPMD/openPMD-api/blob/dev/setup.py
And a new executable named "openpmd-ls" comes in here: openPMD/openPMD-api#574
Axel Huebl
@ax3l
@jaraco do you know how I can express the installation of an externally built executable in setuptools:setup?
Paul Ganssle
@pganssle
@ax3l You can't, really.
It's one of the higher-priority open questions to solve for the Python packaging ecosystem.
Axel Huebl
@ax3l
:'(
Ronny Pfannschmidt
@RonnyPfannschmidt
@pganssle do i recall it correctly that you are trying to solve editable installs for the peps - i was wondering, what if the solution was to generate a special wheel, tagged with +for_editable_install that would contain metadata, a record and the files that the build backend would need to make things work
afterwards that wheel would be installed just like any other wheel, just that instead of shipping the package content, it ships a shim belonging to the controll of the backend
Axel Huebl
@ax3l
@pganssle sorry for the delayed ping, is there a github issue I can subscribe to regarding the install problem I mentioned?