Ben Finney wrote:
[...]
> The perils of duplicate sources of information: a Changelog makes claims
> about which version is latest, but the packaging metadata comes from
> somewhere else.
>
> This problem is addressed quite well, in my opinion, by the Debian
> packaging tools. The tools by default
On Fri, 09 Jan 2015 22:01:38 +1100, Ben Finney wrote:
> alister writes:
>
>> why not simply cheat & call it V 0.2.3 :-) it is not as if there is any
>> regulation concerning what can & cannot constitute a minor release it
>> is all at your own discretion.
>
> Not a regulation, but a convention
alister writes:
> why not simply cheat & call it V 0.2.3 :-) it is not as if there is
> any regulation concerning what can & cannot constitute a minor release
> it is all at your own discretion.
Not a regulation, but a convention which it is good etiquette to follow
http://semver.org/>. Version
On Fri, 09 Jan 2015 11:50:26 +1100, Chris Angelico wrote:
> On Fri, Jan 9, 2015 at 11:41 AM, Steven D'Aprano
> wrote:
>> "oh, pip did the wrong thing again? you can fix that by standing on one
>> leg,
>> sacrificing a goat to the Great Old Dark Ones, deleting these files, or
>> possibly some othe
On Thursday, January 8, 2015 at 7:12:18 PM UTC-6, Ben Finney wrote:
> That does not contradict the position that [python
> packaging] is an ornery beast full of hidden traps and
> compromises though; it just means that everything that
> came before it (in Python) is worse
Ben, you've just proven
On Friday, January 9, 2015 at 6:42:18 AM UTC+5:30, Ben Finney wrote:
> Steven D'Aprano writes:
>
> > Is there a good tutorial to learn about pip?
>
> I'll answer what I think is the correct question: where to learn about
> the current best Python packaging practices.
In order to attain to full I
Steven D'Aprano writes:
> Is there a good tutorial to learn about pip?
I'll answer what I think is the correct question: where to learn about
the current best Python packaging practices.
We have recently gained an official body whose explicit job is to
direct, and be opinionated about, packagin
On Fri, Jan 9, 2015 at 11:41 AM, Steven D'Aprano
wrote:
> "oh, pip did the wrong thing again? you can fix that by standing on one leg,
> sacrificing a goat to the Great Old Dark Ones, deleting these files, or
> possibly some other ones, and if the phase of the moon is exactly right it
> will behav
Irmen de Jong wrote:
> On 8-1-2015 12:16, Steven D'Aprano wrote:
>
>> I screwed up the upload to PyPI, and it won't allow you to upload the
>> same version twice. (At least, I don't know of any way to do so.) So I
>> had to bump the version number to re-upload.
>
> You can manually log into PyPI
Ben Finney wrote:
> Steven D'Aprano writes:
>
>> I screwed up the upload to PyPI, and it won't allow you to upload the
>> same version twice. (At least, I don't know of any way to do so.) So I
>> had to bump the version number to re-upload.
>
> There is currently a hack that can be done (I won'
On Fri, Jan 9, 2015 at 11:06 AM, Ben Finney wrote:
> I've now produced a small Python library which knows how to transform a
> reST Changelog to package metadata; and how to get that package metadata
> into and out of a Python distribution with Distutils.
>
> The result is that I will never again
Steven D'Aprano writes:
> Ben Finney wrote:
> > The source has a ‘CHANGES.txt’ file which has no entry later than
> > version 0.2a. Why was the later version made, and when will the
> > change log be updated for that?
>
> Ah, I knew I forgot something!
The perils of duplicate sources of informat
Steven D'Aprano writes:
> I screwed up the upload to PyPI, and it won't allow you to upload the
> same version twice. (At least, I don't know of any way to do so.) So I
> had to bump the version number to re-upload.
There is currently a hack that can be done (I won't say what it is) to
upload a
On 8-1-2015 12:16, Steven D'Aprano wrote:
> I screwed up the upload to PyPI, and it won't allow you to upload the same
> version twice. (At least, I don't know of any way to do so.) So I had to
> bump the version number to re-upload.
You can manually log into PyPI and fix the uploaded files using
Christian Gollwitzer wrote:
> Hi Steve,
>
> Am 08.01.15 um 05:35 schrieb Steven D'Aprano:
>> At long last, I am pleased to announce the latest version of PyPrimes, a
>> pure Python package for working with prime numbers.
>
> Nice.
>
>> PyPrimes is compatible with Python 2 and 3, and includes mu
Ben Finney wrote:
> Steven D'Aprano writes:
>
>> (Note: pip may have problems downloading the right version if you
>> don't specify a version number.)
>>
>> Or you can access the latest development version:
>>
>> hg clone https://code.google.com/p/pyprimes/
>
> The source has a ‘CHANGES.txt
Hi Steve,
Am 08.01.15 um 05:35 schrieb Steven D'Aprano:
At long last, I am pleased to announce the latest version of PyPrimes, a
pure Python package for working with prime numbers.
Nice.
PyPrimes is compatible with Python 2 and 3, and includes multiple
algorithms for the generating and testi
Steven D'Aprano writes:
> (Note: pip may have problems downloading the right version if you
> don't specify a version number.)
>
> Or you can access the latest development version:
>
> hg clone https://code.google.com/p/pyprimes/
The source has a ‘CHANGES.txt’ file which has no entry later t
At long last, I am pleased to announce the latest version of PyPrimes, a
pure Python package for working with prime numbers.
PyPrimes is compatible with Python 2 and 3, and includes multiple
algorithms for the generating and testing of prime numbers, including the
Sieve of Eratosthenes, Croft S
19 matches
Mail list logo
