[issue20851] Update devguide to cover testing from a tarball

2016-07-22 Thread Brett Cannon

Brett Cannon added the comment:

I don't think this is worth doing.

--
resolution:  -> rejected
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue20851] Update devguide to cover testing from a tarball

2015-08-23 Thread R. David Murray

R. David Murray added the comment:

How to do it is part of PEP 101 (https://www.python.org/dev/peps/pep-0101/).

--
nosy: +r.david.murray

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20851
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue20851] Update devguide to cover testing from a tarball

2015-08-23 Thread Robert Collins

Robert Collins added the comment:

Possibly silly q: how does one /make/ a Python release tarball? 'make dist' 
which is the autoconf standard complains that it has no such target...

--
nosy: +rbcollins

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20851
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue20851] Update devguide to cover testing from a tarball

2015-08-23 Thread Larry Hastings

Larry Hastings added the comment:

To make the tarballs, I use the release.py script from here:

https://hg.python.org/release

and run release.py --export versionnumber.  I haven't peeked inside the 
black box to see how the sausage is made.

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20851
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue20851] Update devguide to cover testing from a tarball

2015-04-22 Thread Brett Cannon

Brett Cannon added the comment:

I don't know if Larry is planning to do tarball releases for 3.5 (added him to 
the nosy to see).

As for the install step, it would be best to suggest people install to a temp 
directory so they don't accidentally end up with a beta release stuck on their 
machines, e.g. `make --prefix=/tmp/cpython`.

--
nosy: +larry

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20851
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue20851] Update devguide to cover testing from a tarball

2015-04-22 Thread Larry Hastings

Larry Hastings added the comment:

I don't plan on doing tarball-only drops during the 3.5 beta/rc period like I 
did during 3.4.  However, when I do a release (e.g. 3.5.0a4), I release Windows 
binaries (built by Steve Dower), OS X binaries (built by Ned Deily), and source 
in tarballs.  If you're on anything but Windows or OS X you have to build it 
yourself, from a tarball.  So it probably makes sense to have instructions in 
the dev guide on how to do it.

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20851
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue20851] Update devguide to cover testing from a tarball

2015-04-21 Thread Carol Willing

Carol Willing added the comment:

Brett, Is documentation for a testing a tarball dumped for an RC still needed? 

If so, are the following steps accurate?

1. Download tarball
2. Extract tarball into a directory
   tar -xzvf release.tar.gz
3. Change directory into release directory
   cd release
4. Install the release
   sudo python setup.py install

My assumption: After installation above, testing should be similar to the 
existing devguide instructions for testing.

Thoughts?

--
nosy: +willingc

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20851
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue20851] Update devguide to cover testing from a tarball

2014-05-09 Thread Ezio Melotti

Changes by Ezio Melotti ezio.melo...@gmail.com:


--
stage:  - needs patch
type:  - enhancement

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20851
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue20851] Update devguide to cover testing from a tarball

2014-03-07 Thread Éric Araujo

Changes by Éric Araujo mer...@netwok.org:


--
nosy: +eric.araujo

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20851
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue20851] Update devguide to cover testing from a tarball

2014-03-04 Thread Brett Cannon

New submission from Brett Cannon:

Nick Coghlan brought up the fact that with Larry Hastings doing periodic 
tarball dumps for the 3.4.0 release it would be good to make sure instructions 
on how to actually test from a tarball were in the devguide.

--
components: Devguide
messages: 212722
nosy: brett.cannon, ezio.melotti
priority: normal
severity: normal
status: open
title: Update devguide to cover testing from a tarball
versions: Python 3.4

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20851
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com