supported workflow for 0.1?

[marianoguerra]

pbt new flask --name myproject # or similar arg structure
cd myproject
pbt install # installs the deps
$EDITOR package.pbt # edit description add deps
pbt install # install new deps
pbt test
pbt run

[marianoguerra]

anything else? @pebete/owners

[StyXman]

Now I see the use of pbt run; for instance, web apps don't have a real main function, but the framework normally gives a way to run a local test server. Cool.

For binaries, pbt run should just run the binary.

I had something else but I forgot.

[jairot]

pbt new flask --name myproject # or similar arg structure
cd myproject
pbt install # installs the deps
$EDITOR package.pbt # edit description add deps
pbt install # install new deps
pbt check #checks the code
pbt test
pbt run
pbt setup # Makes the setup.py
pbt dist #this is not easy

[marianoguerra]

that's why I left it out, we can make 0.2 goal to polish 0.1 and add setup and dist

[marianoguerra]

we need something to show quick before we loose energy so we can get more people on board, without a working prototype nobody will join.

[jairot]

ok, then the workflow is:

pbt new flask --name myproject # or similar arg structure
cd myproject
pbt install # installs the deps
$EDITOR package.pbt # edit description add deps
pbt install # install new deps
pbt check #checks the code
pbt test
pbt run

who works on what? I

[gilgamezh]

I think we could also include 'pbt try'. The plugin should be ready next weekend

[StyXman]

before that workflow, how to install it:

git clone https://github.com/pebete/pbt.git
cd pbt
# optional
./pbt.sh setup
# it would be a user only install; plugins will go to ~/.local
python3 setup.py install [--prefix ...]

[marianoguerra]

why is ./pbt.sh setup optional? what does it do? is this implemented or just a spec of what we should do?

[StyXman]

pbt.sh is the bootstrappintg script. the setup plugin is the one that write the setup.py file. that's in case we decide not to supply it just to show the users the power of pbt :-P

[StyXman]

see #49.

[StyXman]

As discussed, we don't plan to bootstrap pbt with itself. This means that the setup plugin will not be able to write the setup.py file needed to install pbt and its plugins. Instead, that file will be hand crafted, which will not install f.i. the helloworld plugin, which is annoying :)

[jairot]

+1
El 15/04/2014 09:25, "Marcos Dione" [email protected] escribió:

As discussed, we don't plan to bootstrap pbt with itself. This means that
the setup plugin will not be able to write the setup.py file needed to
install pbt and its plugins. Instead, that file will be hand crafted,
which will not install f.i. the helloworld plugin, which is annoying :)

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/53#issuecomment-40475103
.

[jairot]

I had tested the workflow and we are almost there, we are only missing the test command (And the try plugin if we want)

Try it your self! The flask template is working with the new plugin now.

[marianoguerra]

can we close this issue and open issues for specific thigs marked with milestone 0.1

[jairot]

Yes... but I believe that we should have an issue with the "Release
Schedule" for the 0.1 version.

2014-04-27 17:00 GMT-03:00 Mariano Guerra [email protected]:

can we close this issue and open issues for specific thigs marked with
milestone 0.1

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/53#issuecomment-41507143
.

Jairo Trad
Ing. en Computación - FCEFyN - UNC
ar.linkedin.com/in/ingjairotrad