takluyver / flonda Goto Github PK

Conda packages from flit information

License: MIT License

Python 100.00%

flonda's Introduction

Archived: Flonda was an experiment in creating a subset of conda packages without going through a recipe file and conda-build. It didn't take off, and when conda gained support for 'noarch' packages, there was much less need for a tool like this.

Flonda is an experimental tool to publish pure Python code as conda packages

Installation:

pip install flonda

Usage:

First, create Flit metadata for your module or package. Then

# Build conda packages (with flit.ini in CWD)
flonda build

# Set up anaconda.org client
conda install anaconda-client
anaconda login

# Publish packages to anaconda.org
flonda publish

But you probably shouldn't use this yet. It's highly experimental, and you risk building broken packages.

flonda's People

Contributors

Stargazers

Watchers

flonda's Issues

Problem using conda build on windows

Hi,

I'm using windows to upload a package to anaconda and I get the following error:

Packages are now in dist\*\tutormagic-0.3.0-*.tar.bz2
Uploading 5 files to anaconda.org...
Traceback (most recent call last):
  File "d:\users\my_user\appdata\local\continuum\miniconda3\lib\runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "d:\users\my_user\appdata\local\continuum\miniconda3\lib\runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "d:\users\my_user\AppData\Local\Continuum\Miniconda3\Scripts\flonda.exe\__main__.py", line 9, in <module>
  File "d:\users\my_user\appdata\local\continuum\miniconda3\lib\site-packages\flonda\cli.py", line 47, in main
    publish_packages(files)
  File "d:\users\my_user\appdata\local\continuum\miniconda3\lib\site-packages\flonda\cli.py", line 81, in publish_packages
    subprocess.run(['anaconda', 'upload'] + package_files, check=True)
  File "d:\users\my_user\appdata\local\continuum\miniconda3\lib\subprocess.py", line 403, in run
    with Popen(*popenargs, **kwargs) as process:
  File "d:\users\my_user\appdata\local\continuum\miniconda3\lib\subprocess.py", line 707, in __init__
    restore_signals, start_new_session)
  File "d:\users\my_user\appdata\local\continuum\miniconda3\lib\subprocess.py", line 964, in _execute_child
    args = list2cmdline(args)
  File "d:\users\my_user\appdata\local\continuum\miniconda3\lib\subprocess.py", line 461, in list2cmdline
    needquote = (" " in arg) or ("\t" in arg) or not arg
TypeError: argument of type 'WindowsPath' is not iterable

On Linux doing the same I can upload to files to anaconda.

Flonda publish

Now that flit publish uploads a package to PyPI, I'd like a similar command to publish packages on anaconda.org. Something like:

flonda publish [--user anaconda-org-user]

This could either use anaconda-client, or handle the upload directly.

Issue with flit.ini and conda package versions

Hi,

Maybe I'm doing it wrong.

This is my flit.ini file:

[metadata]
module=tutormagic
author=Kiko Correoso
[email protected]
home-page=https://github.com/kikocorreoso/tutormagic
requires=notebook>=4.3.2
requires-python= >=2.7
description-file=README.rst
classifiers=Intended Audience :: Education
    License :: OSI Approved :: MIT License
    Programming Language :: Python :: 2
    Programming Language :: Python :: 2.7
    Programming Language :: Python :: 3
    Programming Language :: Python :: 3.3
    Programming Language :: Python :: 3.4
    Programming Language :: Python :: 3.5
    Programming Language :: Python :: 3.6
    Topic :: Text Processing :: Markup :: HTML

I have checked that notebook version >= 4.3.2 is on conda-forge channel. But when I try to install tutormagic (https://anaconda.org/kikocorreoso/tutormagic) using

conda install -c kikocorreoso tutormagic

it raises:

Fetching package metadata ...............
Solving package specifications:

PackageNotFoundError: Packages missing in current channels:

  - tutormagic -> notebook>=4.3

We have searched for the packages in the following channels:

  - https://conda.anaconda.org/kikocorreoso/win-32
  - https://conda.anaconda.org/kikocorreoso/noarch
  - https://conda.anaconda.org/conda-forge/win-32
  - https://conda.anaconda.org/conda-forge/noarch
  - https://repo.continuum.io/pkgs/free/win-32
  - https://repo.continuum.io/pkgs/free/noarch
  - https://repo.continuum.io/pkgs/r/win-32
  - https://repo.continuum.io/pkgs/r/noarch
  - https://repo.continuum.io/pkgs/pro/win-32
  - https://repo.continuum.io/pkgs/pro/noarch
  - https://repo.continuum.io/pkgs/msys2/win-32
  - https://repo.continuum.io/pkgs/msys2/noarch

I know this is a [risky] package but I was testing it.

Maybe implement rule-based edits of the recipe

Right now, my workflow involves using flit, grayskull, and conda-souschef to package via PyPI, create a skeleton for a conda recipe, and then tweak it programatically. marcelotrevisani/souschef#32

Not sure if flonda could benefit from any of these approaches.

An example using GitHub actions is at https://github.com/sparks-baird/mat_discover/blob/main/.github/workflows/test-publish-release.yml

takluyver / flonda Goto Github PK

flonda's Introduction

flonda's People

Contributors

Stargazers

Watchers

flonda's Issues

Problem using conda build on windows

Flonda publish

Issue with flit.ini and conda package versions

Maybe implement rule-based edits of the recipe

Recommend Projects

React

Vue.js

Typescript

TensorFlow

Django

Laravel

D3

Recommend Topics

javascript

web

server

Machine learning

Visualization

Game

Recommend Org

Facebook

Microsoft

Google

Alibaba

D3

Tencent