15 Matching Annotations
  1. Jul 2020
  2. github.com github.com
    viniciusdc/viniciusdc.github.io
    3
    3. ocefpaf 21 Jul 2020
      SciPy is a community dedicated to the advancement of scientific computing through open source Python software for mathematics, science, and engineering.

      Isso é tirado do site deles em verbatim. Cite com "quotes" ou re-escreve.

    Visit annotations in context

    Annotators

    URL

    github.com/viniciusdc/viniciusdc.github.io/blob/master/_posts/2020-07-20-Scipy-2020.md
  3. Mar 2017
  4. github.com github.com
    sahmed95/gsoc
    8
    1. ocefpaf 17 Mar 2017
      Automatically issue PRs to the feedstocks with package version updates from PyPI. This idea will require reading the package current version from the feedstock, checking if a new version is available and issuing a PR against the feedstock repository. It should follow the MNT PRs model used to re-render feedstocks.

      Same as the GitHub recipe generation goal this one may take a lot of your time. I don't want you to remove it, But keep your deliverable here feasible. Use words like: "start the implementation of..." OK?

    2. ocefpaf 17 Mar 2017
      Add recipe generation from Github repositories. In principle, anybody can use the skeleton to build their forked version of a package but a distinction should be there for the official version of the repository and an user's fork.

      I like the "small steps" you created up to here, but this goal in particular might be trouble some and may be moved down your timeline and added as a "maybe."

      I'l leave that to your best judgement.

    3. ocefpaf 17 Mar 2017
      conda and conda-forge build packages by using a recipe which contains files with information for the build process. A recipe contains build scripts, files specifying metadata and other resources such as README, icon files, or build notes. The template of a recipe is slightly different in conda-forge than that of a conda recipe. Due to this, a heavy editing of recipes is required from the users side.

      Perfect. That states the problem. Maybe you need to change the header from "recipe:" and give this a first class citizen status by naming it "The Problem".

    4. ocefpaf 17 Mar 2017
      unlike conda, with binaries automatically built using free CI tools

      This is not entirely true. Continuum has now open recipes and the use of the word free here is confusing. We have a free account on AppVeyor but Visual Studio, used to build Windows packages, is not free (OSS).

      I see the value in the general idea of this paragraph but you need to make it simpler and mentioned talk about only Continuum maintained recipes vs community maintained recipes.

    6. ocefpaf 17 Mar 2017
      Objectives Creating a conda-smithy skeleton for simplifying the build process for conda-forge packages. Developing tools for conda-forge recipe generation for packages similar to conda skeleton. Simplifying and automating the package updating process by developing tools to regenerate recipes based on the latest package from various sources - PyPI, CRAN, Github.

      Nice and simple. Good!

    7. ocefpaf 17 Mar 2017
      In a similar way, conda-forge recipes are used to build packages using conda-smithy.

      Actually we use conda-skeleton and manual edits. conda-smithy is not used to create the recipes at the moment. (Only to lint it.) (I like your intro. And you can remove this sentence instead of trying to explain what I said above. Let's keep it simple.)

    Visit annotations in context

    Annotators

    URL

    github.com/sahmed95/gsoc/blob/master/2017/proposals/ahmed_shahnawaz.md
  5. Feb 2017
  6. nbviewer.jupyter.org nbviewer.jupyter.org
    Notebook on nbviewer
    2
    1. ocefpaf 10 Feb 2017
      ds_loc=buoy_path, checker_names=['cf', 'acdd'], verbose=True, criteria='normal', skip_checks=None, output_filename=output_file, output_format='text'

      I changed your original call to a more explicit call using named arguments. Just for clarity.

    2. ocefpaf 10 Feb 2017
      # First import the compliance checker and test that it is installed properly.

      Comments like this one are probably better in the Markdown cell rather than code-like comments.

    Visit annotations in context

    Annotators

    URL

    nbviewer.jupyter.org/github/ocefpaf/notebooks_demos/blob/compliance_checker/notebooks/2017-02-10-running_compliance_checker.ipynb
  7. Jan 2016
  8. test.scipyla.org test.scipyla.org
    SciPyLA 2016 [local] | Bem-vindo
    2
    2. ocefpaf 06 Jan 2016
      SciPyLA 2016 is open for sponsorships. If you are interested in supporting this event please contact us at: scipy-organizers@scipy.org See the SciPyLA 2016 Sponsorship Prospectus for more detailed information.

      Não foi traduzido!

    Visit annotations in context

    Annotators

    URL

    test.scipyla.org/scipyla2016/