abravalheri

if(NOT HOME)
  if(WIN32)
    string(REPLACE "\\" "/" HOME "$ENV{USERPROFILE}")
  else()
    set(HOME $ENV{HOME})
  endif()
endif()

### Useful Functions and Macros ###
# Prints a list of messages, each one in a new line

abravalheri

https://github.com/abravalheri/restclient.py/ brainstorm

abravalheri

Commit Message Guidelines

In the last few years, the number of programmers concerned about writing structured commit messages have dramatically grown. As exposed by Tim Pope in article readable commit messages are easy to follow when looking through the project history. Moreover the AngularJS contributing guides introduced conventions that can be used by automation tools to automatically generate useful documentation, or by developers during debugging process.

This document borrows some concepts, conventions and even text mainly from these two sources, extending them in order to provide a sensible guideline for writing commit messages.

• Goals
• Proposal
  • Commit Message Format

• Allowed ``

abravalheri

abravalheri

A variation of the Observer pattern have emerged over the past few yes in the JavaScript community. Called Event Emitter, this pattern seems to simplify the implementation and usage of events.

This is especially true for lightweight libraries in dynamic languages, such as Smoke Signals, where there is no Event object. Instead, plain strings are used to notify the event handlers, which are simple callback functions. The influence of jQuery in this pattern is also remarkable: the features can be accessed in an expressive way with short named methods.

abravalheri

function import(varargin)
 % Import a package. Only entire packages can be imported currently.
 error(nargchk(1, inf, nargin, 'struct'));
 % Import the packages one-by-one
 for i=1:nargin
   import1(varargin{i});
 end
end

function import1(pkgname)

abravalheri

#!/usr/bin/env python3
import io

# Separete the 3 ASCII/ANSI art pokemons originally from
# https://github.com/roberoonska/dotfiles/blob/master/colorscripts/poke

INTRO = """\
#!/bin/sh

initializeANSI()

abravalheri

git config --global alias.lola "log --graph --decorate --pretty=oneline --abbrev-commit --all"

abravalheri

Describe the bug Hello, I have 3 muiltiline docstrings for type aliases (using the next-line """ documentation syntax). For 1 one them the docstring is correctly shown in the rendered HTML, but for 2 of them, the docstrings are ignored and the only thing shown is the alias of ... text. I suppose this is related to #4422, but I might be doing something wrong here (so if you could point me out in the correct direction that would be very good).

To Reproduce The following is a reduced example of something happening in pyscaffold's code base:

1. Given a directory with file.py:

# file.py
from pathlib import Path

abravalheri

title	published	description	tags	cover_image
PyScaffold 4.0 is here 🔥	false	PyScaffold, the Python project template generator with batteries included, just released a new version with lots of new features and it is even easier to use!	python packaging opensource news	https://dev-to-uploads.s3.amazonaws.com/i/qqo4pnhhaxnx1qqc74v7.png

It has been a long journey since PyScaffold v3 was released and a lot of things happened in the Python community especially regarding the packaging ecosystem...